一键导入
perplexity
Use when you need to search the web for current information, verify facts, or look up recent documentation using the pplx-search tool
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when you need to search the web for current information, verify facts, or look up recent documentation using the pplx-search tool
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use for deeper DDD decisions: strategic modeling, subdomains, bounded contexts, and integration risk.
Use when complexity is spreading and you need a simpler model, clearer abstractions, and lower cognitive load.
Use for boundary design, dependency direction, and keeping business policy separate from technical detail.
Use for readability, naming, small functions, and readable behavior-preserving implementations.
Use for disciplined implementation decisions, defensive coding, and maintainable construction choices in real code.
Use when moving from model intent into concrete tactical patterns, events, and distributed integration choices.
| name | perplexity |
| description | Use when you need to search the web for current information, verify facts, or look up recent documentation using the pplx-search tool |
Use pplx-search when you need information that:
Don't use it for: things you already know confidently, general programming concepts, or questions answerable from the codebase itself.
Resolve the CLI before running searches:
PPLX="${PPLX_SEARCH_BIN:-$HOME/.local/bin/pplx-search}"
if [ ! -x "$PPLX" ]; then PPLX="$HOME/.claude/skills/perplexity/pplx-search"; fi
if [ ! -x "$PPLX" ]; then PPLX="$HOME/dotfiles/ai/skills/claude/perplexity/pplx-search"; fi
Prefer "$PPLX" over bare pplx-search because agent shells can start with a minimal PATH.
# Standard search (sonar-pro) — good default for most lookups
"$PPLX" "your query here"
# Fast search (sonar) — quick facts, simple lookups
"$PPLX" -m sonar "is Python 3.13 stable yet"
# Deep research — thorough multi-step investigation
"$PPLX" --deep "comprehensive comparison of Bun vs Deno vs Node in 2025"
# Reasoning — analytical or complex technical questions
"$PPLX" --reason "tradeoffs of ECS vs OOP for game engine architecture"
# Pipe context in
echo "explain this error: $ERROR_MSG" | "$PPLX" --stdin
# Raw JSON output (if you need to parse programmatically)
"$PPLX" --json "query"
# Local setup check, no API request
"$PPLX" --health
Short, specific queries get the best results. Include version numbers, language names, and framework names when relevant.
| Bad | Good |
|---|---|
| "how to do auth" | "NextJS 15 app router authentication with Auth.js" |
| "rust error" | "rust borrow checker error returning reference to local variable" |
| "is this deprecated" | "is React.createClass deprecated in React 19" |
The tool returns markdown with:
| Flag | Model | Use When |
|---|---|---|
| (default) | sonar-pro | General searches, docs, how-tos |
-m sonar | sonar | Quick facts, simple yes/no, fast lookups |
--deep | sonar-deep-research | Thorough comparisons, research-grade answers |
--reason | sonar-reasoning-pro | Complex analysis, architecture decisions, "why" questions |
Default is sonar-pro which balances speed and quality well.
export PERPLEXITY_API_KEY="pplx-..."tools/perplexity/ to your PATH or call it directly as ./tools/perplexity/pplx-searchNo pip install. No dependencies. Just Python 3.9+.
Perplexity API is pay-per-use. Approximate costs:
The token count in the output footer helps you track spend. Prefer sonar for quick checks and sonar-pro as your default. Reserve --deep for when you really need it.