perplexity — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited perplexity (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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).
Which Perplexity tool?
/research <topic>)NOT Perplexity - use these instead:
gt CLI → Graphite MCPWhen to use:
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:
// Increased limits (use sparingly)
mcp__perplexity__perplexity_search({
query: "complex topic",
max_results: 5,
max_tokens_per_page: 1024
})When to use:
Usage:
mcp__perplexity__perplexity_ask({
messages: [
{
role: "user",
content: "Explain how postgres advisory locks work"
}
]
})NOT for:
NEVER use: mcp__perplexity__perplexity_research
Use instead: Researcher agent (/research <topic>)
Priority order:
gt CLI mention✅ CORRECT - Use Perplexity Search:
✅ CORRECT - Use Perplexity Ask:
❌ WRONG - Use Context7 instead:
❌ WRONG - Use Graphite MCP instead:
❌ WRONG - Use Nx MCP instead:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.