What problem does it solve? It prevents wasted tokens and wrong tool choices when handling web search requests by defining exactly when to use Perplexity Search, Perplexity Ask, or a different specialized tool like Context7, Graphite MCP, or Nx MCP. ## Core Features & Use Cases - Tool selection chain: Enforces a priority order (Context7, Graphite MCP, Nx MCP, then Perplexity) so library docs and workspace questions never hit the wrong API. - Token budget control: Mandates conservative defaults (max_results: 3, max_tokens_per_page: 512) to avoid context bloat from oversized search results. - Research cost guardrail: Prohibits the expensive perplexity_research tool (30-50k tokens) and delegates deep research to the /research agent instead. - Use Case: When a user says "find postgres migration best practices", the skill routes to Perplexity Search with limited results; when they ask about React hooks docs, it redirects to Context7 instead. ## Quick Start Ask the assistant to search for a current topic, such as "search for the latest microservices trends", and it will apply the correct Perplexity tool with conservative limits.