Use for substantial investigations needing current evidence, source comparison, or synthesis across several dimensions. Scale research to the question and requested depth.
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/public/deep-research/SKILL.mdThis skill provides a systematic methodology for conducting thorough web research. Use it when the requested claims need external verification; use supplied material and stable knowledge where sufficient.
Consider this skill when depth and external verification are needed:
Choose effort according to freshness, uncertainty, consequence, and scope. A focused question may be resolved by one authoritative source; broad or disputed claims need independent checks. Stop when requested claims have sufficient support and state remaining gaps.
Start with broad searches to understand the landscape:
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 considerationsFor each important dimension identified, conduct targeted research:
web_fetch to read important sources in full, not just snippetsExample:
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 studiesEnsure 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" |
Before proceeding to content generation, verify:
Investigate material evidence gaps; omit irrelevant checklist items and disclose unresolved limits.
# 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"For time-sensitive questions, use the actual current date and the requested time range when choosing search filters.
<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:
"tech news 2026" will NOT surface today's news2026-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
Use web_fetch to read full content when:
Research is iterative. After initial searches:
Your research is sufficient when you can confidently answer:
After completing research, you should have:
Produce the requested output once its factual claims have adequate support; adapt these phases to the task.
bytedance/deer-flow
085b52b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.