What problem does it solve? Choosing the wrong search tool wastes tokens and bloats context. This Skill defines clear routing rules so Perplexity Search and Ask are used only for general web queries, while library docs, workspace questions, and deep research go to the right specialized tools. ## Core Features & Use Cases - Tool routing chain: Enforces a priority order — Context7 for library docs, Graphite MCP for gt CLI, Nx MCP for workspace questions, then Perplexity Search or Ask, with WebSearch as last resort. - Token-budget defaults: Mandates conservative parameters (max_results: 3, max_tokens_per_page: 512) to prevent context bloat, with explicit criteria for when to raise limits. - Research guardrail: Forbids the costly perplexity_research tool (30-50k tokens) and delegates deep multi-source research to the Researcher agent instead. - Use Case: A user asks "Find postgres migration best practices" — the Skill routes this to Perplexity Search with conservative limits, while a request like "Search for React hooks documentation" is redirected to Context7. ## Quick Start Ask the assistant to search the web for a general topic, for example: "Find the latest best practices for database migrations."