deep-research
Use this skill instead of WebSearch for ANY question requiring web research. Trigger on queries like "what is X", "explain X", "compare X and Y", "research X", or before content generation tasks. Provides systematic multi-angle research methodology instead of single superficial searches. Use this proactively when the user's question needs online information.
What this skill does
# Deep Research Skill ## Overview This skill provides a systematic methodology for conducting thorough web research. **Load this skill BEFORE starting any content generation task** to ensure you gather sufficient information from multiple angles, depths, and sources. ## When to Use This Skill **Always load this skill when:** ### Research Questions - User asks "what is X", "explain X", "research X", "investigate X" - User wants to understand a concept, technology, or topic in depth - The question requires current, comprehensive information from multiple sources - A single web search would be insufficient to answer properly ### Content Generation (Pre-research) - Creating presentations (PPT/slides) - Creating frontend designs or UI mockups - Writing articles, reports, or documentation - Producing videos or multimedia content - Any content that requires real-world information, examples, or current data ## Core Principle **Never generate content based solely on general knowledge.** The quality of your output directly depends on the quality and quantity of research conducted beforehand. A single search query is NEVER enough. ## Research Methodology ### Phase 1: Broad Exploration Start with broad searches to understand the landscape: 1. **Initial Survey**: Search for the main topic to understand the overall context 2. **Identify Dimensions**: From initial results, identify key subtopics, themes, angles, or aspects that need deeper exploration 3. **Map the Territory**: Note different perspectives, stakeholders, or viewpoints that exist Example: ``` Topic: "AI in healthcare" Initial searches: - "AI healthcare applications 2024" - "artificial intelligence medical diagnosis" - "healthcare AI market trends" Identified dimensions: - Diagnostic AI (radiology, pathology) - Treatment recommendation systems - Administrative automation - Patient monitoring - Regulatory landscape - Ethical considerations ``` ### Phase 2: Deep Dive For each important dimension identified, conduct targeted research: 1. **Specific Queries**: Search with precise keywords for each subtopic 2. **Multiple Phrasings**: Try different keyword combinations and phrasings 3. **Fetch Full Content**: Use `web_fetch` to read important sources in full, not just snippets 4. **Follow References**: When sources mention other important resources, search for those too Example: ``` Dimension: "Diagnostic AI in radiology" Targeted searches: - "AI radiology FDA approved systems" - "chest X-ray AI detection accuracy" - "radiology AI clinical trials results" Then fetch and read: - Key research papers or summaries - Industry reports - Real-world case studies ``` ### Phase 3: Diversity & Validation Ensure comprehensive coverage by seeking diverse information types: | Information Type | Purpose | Example Searches | |-----------------|---------|------------------| | **Facts & Data** | Concrete evidence | "statistics", "data", "numbers", "market size" | | **Examples & Cases** | Real-world applications | "case study", "example", "implementation" | | **Expert Opinions** | Authority perspectives | "expert analysis", "interview", "commentary" | | **Trends & Predictions** | Future direction | "trends 2024", "forecast", "future of" | | **Comparisons** | Context and alternatives | "vs", "comparison", "alternatives" | | **Challenges & Criticisms** | Balanced view | "challenges", "limitations", "criticism" | ### Phase 4: Synthesis Check Before proceeding to content generation, verify: - [ ] Have I searched from at least 3-5 different angles? - [ ] Have I fetched and read the most important sources in full? - [ ] Do I have concrete data, examples, and expert perspectives? - [ ] Have I explored both positive aspects and challenges/limitations? - [ ] Is my information current and from authoritative sources? **If any answer is NO, continue researching before generating content.** ## Search Strategy Tips ### Effective Query Patterns ``` # Be specific with context ❌ "AI trends" ✅ "enterprise AI adoption trends 2024" # Include authoritative source hints "[topic] research paper" "[topic] McKinsey report" "[topic] industry analysis" # Search for specific content types "[topic] case study" "[topic] statistics" "[topic] expert interview" # Use temporal qualifiers — always use the ACTUAL current year from <current_date> "[topic] 2026" # ← replace with real current year, never hardcode a past year "[topic] latest" "[topic] recent developments" ``` ### Temporal Awareness **Always check `<current_date>` in your context before forming ANY search query.** `<current_date>` gives you the full date: year, month, day, and weekday (e.g. `2026-02-28, Saturday`). Use the right level of precision depending on what the user is asking: | User intent | Temporal precision needed | Example query | |---|---|---| | "today / this morning / just released" | **Month + Day** | `"tech news February 28 2026"` | | "this week" | **Week range** | `"technology releases week of Feb 24 2026"` | | "recently / latest / new" | **Month** | `"AI breakthroughs February 2026"` | | "this year / trends" | **Year** | `"software trends 2026"` | **Rules:** - When the user asks about "today" or "just released", use **month + day + year** in your search queries to get same-day results - Never drop to year-only when day-level precision is needed — `"tech news 2026"` will NOT surface today's news - Try multiple phrasings: numeric form (`2026-02-28`), written form (`February 28 2026`), and relative terms (`today`, `this week`) across different queries ❌ User asks "what's new in tech today" → searching `"new technology 2026"` → misses today's news ✅ User asks "what's new in tech today" → searching `"new technology February 28 2026"` + `"tech news today Feb 28"` → gets today's results ### When to Use web_fetch Use `web_fetch` to read full content when: - A search result looks highly relevant and authoritative - You need detailed information beyond the snippet - The source contains data, case studies, or expert analysis - You want to understand the full context of a finding ### Iterative Refinement Research is iterative. After initial searches: 1. Review what you've learned 2. Identify gaps in your understanding 3. Formulate new, more targeted queries 4. Repeat until you have comprehensive coverage ## Quality Bar Your research is sufficient when you can confidently answer: - What are the key facts and data points? - What are 2-3 concrete real-world examples? - What do experts say about this topic? - What are the current trends and future directions? - What are the challenges or limitations? - What makes this topic relevant or important now? ## Common Mistakes to Avoid - ❌ Stopping after 1-2 searches - ❌ Relying on search snippets without reading full sources - ❌ Searching only one aspect of a multi-faceted topic - ❌ Ignoring contradicting viewpoints or challenges - ❌ Using outdated information when current data exists - ❌ Starting content generation before research is complete ## Output After completing research, you should have: 1. A comprehensive understanding of the topic from multiple angles 2. Specific facts, data points, and statistics 3. Real-world examples and case studies 4. Expert perspectives and authoritative sources 5. Current trends and relevant context **Only then proceed to content generation**, using the gathered information to create high-quality, well-informed content.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.