Searching Deeply
Iterative parallel search strategy using WebSearch and Exa. Launch multiple searches simultaneously, learn from failures, and keep iterating until finding answers. Use for research, code examples, documentation, and technical information gathering.
What this skill does
# Searching Deeply ## Core Strategy **Search in parallel. Learn from failures. Keep iterating.** Never give up after one search round. Launch new searches based on what worked and what didn't. ## Available Tools - **WebSearch** - General info, news, tutorials, overviews (free, fast) - **mcp__exa__get_code_context_exa** - Code examples, implementations ($0.01/query) - **mcp__exa__web_search_exa** - Academic papers, technical docs ($0.01/query) ## Related Skills & Snippets - **google-scholar** skill - For academic paper research with citation tracking - **DOWNLOAD** snippet - For downloading PDFs from Anna's Archive - **document-skills:pdf** - For extracting text from downloaded papers ## Iterative Workflow ### Round 1: Launch Parallel Searches Start with 3-5 searches from different angles: **General topics:** - WebSearch with variations of query - Different phrasings, synonyms, related terms - Add context: year "2024 2025", tech stack, keywords **Code/implementation:** - WebSearch for overview/tutorial - mcp__exa__get_code_context_exa for real examples **Academic/research:** - WebSearch for overview - mcp__exa__web_search_exa for papers - Use google-scholar skill for deeper research ### Round 2: Analyze & Iterate **What did you learn?** - New terminology discovered? - Specific authors/sources mentioned? - Related topics to explore? **What's missing?** - Gaps in understanding - Unanswered questions - Need more examples/evidence **Launch next round:** - Reformulate queries with new terms - Search for specific gaps - Try broader or narrower scope - 3-5 new parallel searches ### Round 3+: Keep Going **Don't stop until:** - Question fully answered - Multiple sources confirm findings - Examples found and verified - All gaps identified and filled **If stuck:** - Try different keywords/synonyms - Split complex query into parts - Search related topics first - Switch tools (WebSearch ↔ Exa) - Check alternative sources ## Query Optimization **Make queries specific:** - ❌ "authentication" - ✅ "JWT authentication Express.js tutorial 2025" **Add context:** - Technology: "Node.js", "Python", "React" - Timeframe: "2024 2025" for recent - Type: "tutorial", "example", "production", "best practices" **Use domain filtering:** - Academic: `allowed_domains: ["*.edu", "arxiv.org"]` - Developer: `allowed_domains: ["github.com", "dev.to"]` ## Persistence Rules **Never give up after one failed search.** If results are poor: 1. Try different keywords 2. Broaden or narrow scope 3. Split into smaller questions 4. Switch tools 5. Search related topics first **Keep iterating until satisfied.** ## Common Research Patterns ### Quick Answer Single focused WebSearch with specific query ### General Research - 3-5 parallel WebSearch with different angles - Iterate based on results ### Code Research - WebSearch for overview - mcp__exa__get_code_context_exa for examples - Iterate for edge cases, error handling ### Academic Research - WebSearch for overview - mcp__exa__web_search_exa for papers - Use **google-scholar** skill for citations - Use **DOWNLOAD** snippet for PDFs - Use **document-skills:pdf** to extract content ## Example: Iterative Search **Round 1:** ``` WebSearch: "Python async programming" → Learned: asyncio is the main library ``` **Round 2:** ``` WebSearch: "Python asyncio tutorial 2025" WebSearch: "asyncio vs threading when to use" mcp__exa__get_code_context_exa: "Python asyncio examples" → Learned: Good basics, but need error handling ``` **Round 3:** ``` WebSearch: "asyncio error handling best practices" WebSearch: "asyncio common mistakes" mcp__exa__get_code_context_exa: "asyncio exception handling" → Complete understanding achieved ``` ## Validation Cross-reference findings: - Check multiple sources - Verify recent dates (2024-2025) - Look for authoritative sources - Test code examples - Confirm consistency ## Quick Reference **Default:** 3-5 parallel WebSearch with different angles **For code:** Add mcp__exa__get_code_context_exa **For papers:** Add mcp__exa__web_search_exa or use google-scholar skill **For PDFs:** Use DOWNLOAD snippet **When stuck:** Reformulate, try new terms, iterate **Remember:** Keep going until you find complete answers
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.