perplexity

softaworks/agent-toolkit · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/softaworks/agent-toolkit --skill perplexity
0 commentsdiscussion
summary

Use ONLY when user says "search", "find", "look up", "ask", "research", or "what's the latest" for generic queries. NOT for library/framework docs (use Context7), gt CLI (use Graphite MCP), or workspace questions (use Nx MCP).

skill.md

Perplexity Tools

Use ONLY when user says "search", "find", "look up", "ask", "research", or "what's the latest" for generic queries. NOT for library/framework docs (use Context7), gt CLI (use Graphite MCP), or workspace questions (use Nx MCP).

Quick Reference

Which Perplexity tool?

  • Need search results/URLs? → Perplexity Search
  • Need conversational answer? → Perplexity Ask
  • Need deep research? → Researcher agent (/research <topic>)

NOT Perplexity - use these instead:

  • Library/framework docs → Context7 MCP
  • Graphite gt CLI → Graphite MCP
  • THIS workspace → Nx MCP
  • Specific URL → URL Crawler

Perplexity Search

When to use:

  • Generic searches, finding resources
  • Current best practices, recent information
  • Tutorial/blog post discovery
  • User says "search for...", "find...", "look up..."

Default parameters (ALWAYS USE):

mcp__perplexity__perplexity_search({
  query: "your search query",
  max_results: 3,           // Default is 10 - too many!
  max_tokens_per_page: 512  // Reduce per-result content
})

When to increase limits: Only if:

  • User explicitly needs comprehensive results
  • Initial search found nothing useful
  • Complex topic needs multiple sources
// Increased limits (use sparingly)
mcp__perplexity__perplexity_search({
  query: "complex topic",
  max_results: 5,
  max_tokens_per_page: 1024
})

Perplexity Ask

When to use:

  • Need conversational explanation, not search results
  • Synthesize information from web
  • Explain concepts with current context

Usage:

mcp__perplexity__perplexity_ask({
  messages: [
    {
      role: "user",
      content: "Explain how postgres advisory locks work"
    }
  ]
})

NOT for:

  • Library documentation (use Context7)
  • Deep multi-source research (use researcher agent)

Prohibited Tool

NEVER use: mcp__perplexity__perplexity_research

Use instead: Researcher agent (/research <topic>)

  • Token cost: 30-50k tokens
  • Provides multi-source synthesis with citations
  • Use sparingly for complex questions only

Tool Selection Chain

Priority order:

  1. Context7 MCP - Library/framework docs
  2. Graphite MCP - Any gt CLI mention
  3. Nx MCP - THIS workspace questions
  4. Perplexity Search - Generic searches
  5. Perplexity Ask - Conversational answers
  6. Researcher agent - Deep multi-source research
  7. WebSearch - Last resort (after Perplexity exhausted)

Examples

✅ CORRECT - Use Perplexity Search:

  • "Find postgres migration best practices"
  • "Search for React testing tutorials"
  • "Look up latest trends in microservices"

✅ CORRECT - Use Perplexity Ask:

  • "Explain how postgres advisory locks work"
  • "What are the trade-offs of microservices?"

❌ WRONG - Use Context7 instead:

  • "Search for React hooks documentation" → Context7 MCP
  • "Find Next.js routing docs" → Context7 MCP
  • "Look up Temporal workflow API" → Context7 MCP

❌ WRONG - Use Graphite MCP instead:

  • "Search for gt stack commands" → Graphite MCP
  • "Find gt branch workflow" → Graphite MCP

❌ WRONG - Use Nx MCP instead:

  • "Search for build config" (in THIS workspace) → Nx MCP
  • "Find project dependencies" (in THIS workspace) → Nx MCP

Key Points

  • Default to limited results - avoid context bloat
  • Library docs = Context7 - ALWAYS try Context7 first
  • "gt" = Graphite MCP - ANY "gt" mention uses Graphite
  • Deep research = /research - NOT perplexity_research tool
  • Fallback chain - Search → Ask → WebSearch (last resort)
how to use perplexity

How to use perplexity on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add perplexity
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/softaworks/agent-toolkit --skill perplexity

The skills CLI fetches perplexity from GitHub repository softaworks/agent-toolkit and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/perplexity

Reload or restart Cursor to activate perplexity. Access the skill through slash commands (e.g., /perplexity) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.733 reviews
  • Mei Okafor· Dec 24, 2024

    Useful defaults in perplexity — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Alexander Diallo· Sep 17, 2024

    perplexity is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Oshnikdeep· Sep 9, 2024

    Keeps context tight: perplexity is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Luis Robinson· Sep 1, 2024

    perplexity reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ganesh Mohane· Aug 28, 2024

    We added perplexity from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Mateo Ramirez· Aug 20, 2024

    perplexity is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Charlotte Gonzalez· Aug 8, 2024

    perplexity reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Alexander Rahman· Jul 27, 2024

    We added perplexity from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Jul 19, 2024

    perplexity reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kabir Taylor· Jul 11, 2024

    Keeps context tight: perplexity is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 33

1 / 4