web-research
Use this skill for requests related to web research; it provides a structured approach to conducting comprehensive web research
What this skill does
# Web Research Skill This skill provides a structured approach to conducting comprehensive web research using the `task` tool to spawn research subagents. It emphasizes planning, efficient delegation, and systematic synthesis of findings. ## When to Use This Skill Use this skill when you need to: - Research complex topics requiring multiple information sources - Gather and synthesize current information from the web - Conduct comparative analysis across multiple subjects - Produce well-sourced research reports with clear citations ## Research Process ### Step 1: Create and Save Research Plan Before delegating to subagents, you MUST: 1. **Create a research folder** - Organize all research files in a dedicated folder relative to the current working directory: ``` mkdir research_[topic_name] ``` This keeps files organized and prevents clutter in the working directory. 2. **Analyze the research question** - Break it down into distinct, non-overlapping subtopics 3. **Write a research plan file** - Use the `write_file` tool to create `research_[topic_name]/research_plan.md` containing: - The main research question - 2-5 specific subtopics to investigate - Expected information from each subtopic - How results will be synthesized **Planning Guidelines:** - **Simple fact-finding**: 1-2 subtopics - **Comparative analysis**: 1 subtopic per comparison element (max 3) - **Complex investigations**: 3-5 subtopics ### Step 2: Delegate to Research Subagents For each subtopic in your plan: 1. **Use the `task` tool** to spawn a research subagent with: - Clear, specific research question (no acronyms) - Instructions to write findings to a file: `research_[topic_name]/findings_[subtopic].md` - Budget: 3-5 web searches maximum 2. **Run up to 3 subagents in parallel** for efficient research **Subagent Instructions Template:** ``` Research [SPECIFIC TOPIC]. Use the web_search tool to gather information. After completing your research, use write_file to save your findings to research_[topic_name]/findings_[subtopic].md. Include key facts, relevant quotes, and source URLs. Use 3-5 web searches maximum. ``` ### Step 3: Synthesize Findings After all subagents complete: 1. **Review the findings files** that were saved locally: - First run `list_files research_[topic_name]` to see what files were created - Then use `read_file` with the **file paths** (e.g., `research_[topic_name]/findings_*.md`) - **Important**: Use `read_file` for LOCAL files only, not URLs 2. **Synthesize the information** - Create a comprehensive response that: - Directly answers the original question - Integrates insights from all subtopics - Cites specific sources with URLs (from the findings files) - Identifies any gaps or limitations 3. **Write final report** (optional) - Use `write_file` to create `research_[topic_name]/research_report.md` if requested **Note**: If you need to fetch additional information from URLs, use the `fetch_url` tool, not `read_file`. ## Available Tools You have access to: - **write_file**: Save research plans and findings to local files - **read_file**: Read local files (e.g., findings saved by subagents) - **list_files**: See what local files exist in a directory - **fetch_url**: Fetch content from URLs and convert to markdown (use this for web pages, not read_file) - **task**: Spawn research subagents with web_search access ## Research Subagent Configuration Each subagent you spawn will have access to: - **web_search**: Search the web using Tavily (parameters: query, max_results, topic, include_raw_content) - **write_file**: Save their findings to the filesystem ## Best Practices - **Plan before delegating** - Always write research_plan.md first - **Clear subtopics** - Ensure each subagent has distinct, non-overlapping scope - **File-based communication** - Have subagents save findings to files, not return them directly - **Systematic synthesis** - Read all findings files before creating final response - **Stop appropriately** - Don't over-research; 3-5 searches per subtopic is usually sufficient
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.