AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Perplexity Research

skill-zacharygcook-agent-skills-perplexity-research · by zacharygcook

Use Perplexity MCP for current, cited web research. Trigger when the user asks to use Perplexity, asks for deep research, market/vendor/provider research, current comparisons, current API/service capability checks, or wants citation-backed investigation beyond ordinary browsing.

↗ Repository
— No reviews yet
0 installs
15 views
0.0% view→install

Install

$ agentstack add skill-zacharygcook-agent-skills-perplexity-research

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ● Environment & secrets Used
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-zacharygcook-agent-skills-perplexity-research)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 28d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Perplexity Research? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Perplexity Research

Use the Perplexity MCP server for research that benefits from current web search, source synthesis, and citations. Prefer it for vendor/provider comparisons, service capability research, recent API documentation checks, and broad market scans.

MCP Setup Assumption

The local Codex MCP server is named perplexity.

If Perplexity tools are not already exposed, discover them with tool_search using a query like perplexity research. Expected tools from the MCP server:

  • perplexity_search: ranked web search results.
  • perplexity_ask: quick web-grounded answers.
  • perplexity_research: deeper cited research reports.
  • perplexity_reason: reasoning-heavy analysis.

If the server fails because PERPLEXITY_API_KEY is missing, tell the user to add a real key to ~/.perplexity-mcp.env and restart Codex/MCP. Do not invent Perplexity results if the MCP is unavailable.

Tool Choice

  • Use perplexity_research for comprehensive vendor/provider research, due diligence, competitive comparisons, or questions with high business impact.
  • Deep research can take several minutes. If the current tool surface times out around 300 seconds and does not expose a per-call timeout, treat that as an environment/tooling limit, not a research answer.
  • On deep-research timeout, fall back to perplexity_reason with search_context_size: "high" for comparative analysis, or perplexity_ask with search_context_size: "high" for source-grounded factual summaries.
  • Use perplexity_search first when you need a short source list before deeper investigation.
  • Use perplexity_ask for narrow factual questions.
  • Use perplexity_reason when the user asks for strategy, tradeoffs, ranking logic, or decision support after evidence has been gathered.

Research Standards

  • Prefer primary sources: official docs, pricing pages, API references, provider terms, and public product pages.
  • Use secondary sources only to fill market context, not as proof of API capability.
  • Distinguish confirmed facts from inference.
  • Preserve source URLs in the final answer.
  • For API/vendor work, verify:
  • supported input identifiers,
  • response objects/fields,
  • whether the provider finds people, relatives, owners, heirs, or only enriches known people,
  • pricing model,
  • API availability,
  • batch versus synchronous mode,
  • fit for the user's actual workflow.

Output Shape

For vendor/provider research, return:

  1. Short conclusion.
  2. Ranked options with best use case and caveats.
  3. Table of confirmed capabilities.
  4. Recommended workflow or waterfall.
  5. Open questions to verify with sales/support or API samples.
  6. Source links.

Do not overstate "heir" capability. If a provider returns relatives, household members, associates, owners, or enriched person profiles, label that precisely.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills