deep-research
Skill821 starsChanged 8 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Start with broad searches to understand the landscape:
- Distinctive: line 39
Initial Survey: Search for the main topic to understand the overall context
- Distinctive: line 64
Specific Queries: Search with precise keywords for each subtopic
- Very specific: line 66
Fetch Full Content: Use web_fetch to read important sources in full, not just snippets
- Distinctive: line 67
Follow References: When sources mention other important resources, search for those too
- Distinctive: line 85
Ensure comprehensive coverage by seeking diverse information types:
- Distinctive: line 98
Before proceeding to content generation, verify:
- Distinctive: line 147
When the user asks about "today" or "just released", use month + day + year in your search queries to get same-day results
- Very specific: line 148
Never drop to year-only when day-level precision is needed — "tech news 2026" will NOT surface today's news
- Very specific: line 156
Use web_fetch to read full content when:
- Distinctive: line 191
After completing research, you should have:
“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- Initial Survey: Search for the main topic to understand the overall context
- Identify Dimensions: From initial results, identify key subtopics, themes, angles, or aspects that need deeper exploration
- 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 considerationsPhase 2: Deep Dive
For each important dimension identified, conduct targeted research:
- Specific Queries: Search with precise keywords for each subtopic
- Multiple Phrasings: Try different keyword combinations and phrasings
- Fetch Full Content: Use
web_fetchto read important sources in full, not just snippets - 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 studiesPhase 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:
- Review what you've learned
- Identify gaps in your understanding
- Formulate new, more targeted queries
- 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:
- A comprehensive understanding of the topic from multiple angles
- Specific facts, data points, and statistics
- Real-world examples and case studies
- Expert perspectives and authoritative sources
- Current trends and relevant context
Only then proceed to content generation, using the gathered information to create high-quality, well-informed content.
Trending
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Other versions196 projects use a version of this.
Word for word · 2
- bytedance/deer-flow★ 85k100% same
- CreamyLong/quill★ 2100% same
Edited · 0
None found.
Wrote their own version · 194
- affaan-m/ECC★ 246ksame name
- Imbad0202/academic-research-skills★ 55ksame name
- THU-MAIC/OpenMAIC★ 41ksame name
- genspark-ai/genoffice★ 11ksame name
- HKUSTDial/Supervisor-Skills★ 11ksame name
- getcompanion-ai/feynman★ 10ksame name
- advaitpaliwal/feynman★ 10ksame name
- companion-inc/feynman★ 10ksame name
- jordan-gibbs/hyperresearch★ 4.2ksame name
- davidondrej/skills★ 4.2ksame name
184 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use community-led-growth, ph-community-outreach and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
zebbernSkillacademic-paper-reviewer
Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to \"review my paper,\" \"simulate peer review,\" or \"give my paper a peer review.
Also in 9 projects that use this
W-MoorerSkillacademic-pipeline
Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory integrity verification, two-stage peer review, and reproducible quality gates. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow.
Also in 8 projects that use this
ncklrsSkillseo-content-strategist
Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.
Also in 5 projects that use this
xfstudioSkillmicro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Also in 5 projects that use this
- +4 more from nicepkg
In this repository25 other files it gives its agents.
- backend/AGENTS.mdAGENTS.md
- frontend/AGENTS.mdAGENTS.md
- backend/CLAUDE.mdCLAUDE.md
- frontend/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- bootstrapSkill
- chart-visualizationSkill
- claude-to-deerflowSkill
- company-researchSkill
- consulting-analysisSkill
- data-analysisSkill
- find-skillsSkill
- frontend-designSkill
- github-deep-researchSkill
- image-generationSkill
- multi-languageSkill
- paper-researchSkill
- podcast-generationSkill
- ppt-generationSkill
- report-to-pptSkill
- skill-creatorSkill
- surprise-meSkill
- vercel-deploySkill
- video-generationSkill
- web-design-guidelinesSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

