perplexity
Web search and research using Perplexity AI. Use when user says "search", "find", "look up", "ask", "research", or "what's the latest" for generic queries. NOT for library/framework docs (use Context7) or workspace questions.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 3.3w
- Forks
- 3.9k
01 前言 Front Matter
- name
- perplexity
- description
- Web search and research using Perplexity AI. Use when user says "search", "find", "look up", "ask", "research", or "what's the latest" for generic queries. NOT for library/framework docs (use Context7) or workspace questions.
02 资源文件 1
- 参考文档README.md6.0 KB
03 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
gtCLI → 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:
- Context7 MCP - Library/framework docs
- Graphite MCP - Any
gtCLI mention - Nx MCP - THIS workspace questions
- Perplexity Search - Generic searches
- Perplexity Ask - Conversational answers
- Researcher agent - Deep multi-source research
- 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)
04 同仓库更多 Skills
wealthville-pool-scoring
Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.
technical-debt-auditor
Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.
readonly-sql-guard
Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
discernment-nudge
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.