deep-research
Skill0 starsChanged 38 days agoMITView on GitHub
Runs a thorough multi-source research process - decompose the question, gather independent sources, cross-check, synthesize - and delivers a structured, cited brief with confidence levels and gaps. Use when someone asks "research this topic in depth", "give me everything on X", "what does the evidence say about Y", or needs a broad question answered from secondary sources with citations. Do NOT use for designing a study that collects new data - use primary-research instead; for distilling an already-gathered pile of 20+ sources into themes, use research-synthesis; for verifying one discrete claim, use fact-checker.
196 other projects use a version of this.
Adopted by
Most recently taken up by
- ridelink0/ultimate-frontend-skillstheir own version, first seen Nov 8, 2026
- chrisblattman/claudeblattmantheir own version, first seen Nov 8, 2026
- genericService/claude-skillstheir own version, first seen Nov 8, 2026
- ourostack/ouroboros-skillstheir own version, first seen Nov 8, 2026
- mahsumaktas/agent-evolution-kittheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use community-led-growth, ph-community-outreach and 10 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
W-MoorerSkillacademic-paper-reviewer
Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy.
Also in 11 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 10 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
stophobiaSkillsurprise-me
Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for "something interesting".
Also in 4 projects that use this
- +4 more from nicepkg
- +1 more from W-Moorer
Other versions196 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 196
- affaan-m/ECC★ 246ksame name
- bytedance/deer-flow★ 85ksame name
- Imbad0202/academic-research-skills★ 56ksame name
- THU-MAIC/OpenMAIC★ 43ksame name
- HKUSTDial/Supervisor-Skills★ 12ksame name
- genspark-ai/genoffice★ 12ksame name
- advaitpaliwal/feynman★ 10ksame name
- companion-inc/feynman★ 10ksame name
- getcompanion-ai/feynman★ 10ksame name
- jordan-gibbs/hyperresearch★ 4.4ksame name
186 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.
In this repository5 other files it gives its agents.
- agent-orchestrationSkill
- error-handlingSkill
- llm-evaluationSkill
- ml-feature-engineeringSkill
- prompt-engineerSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 177 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 57
Do not invent or embellish a citation - one fabricated source invalidates the entire brief.
- Distinctive: line 58
Do not count correlated sources as corroboration.
- Distinctive: line 59
Do not average disagreeing sources into a mushy middle.
- Distinctive: line 60
Do not let the gathering order set the narrative - the first three sources found are the most findable ones, not the most representative.
- Distinctive: line 61
Do not blur evidence and inference.
“Common” is measured: kept by at least 6 in 10 of the 177 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
Go wide, then deep: triangulate across independent sources and report what was actually found, including the gaps. The costly failure this skill prevents is the confident brief built on an echo - a dozen articles that all trace to one blog post or one press release, presented as consensus. "Not found" is a legitimate finding; a smooth answer papering over thin evidence is not.
Inputs to collect
- The research question, restated until the user confirms it. Ambiguity here multiplies through every later step.
- What decision or output the research feeds. A brief informing a purchase differs from one informing a publication.
- Scope boundaries: geography, industry, population, and what is explicitly out of scope.
- Depth and deadline. Default: 3-6 sub-questions, at least two independent sources per sub-question.
- Known sources or prior work to build on. Treat supplied sources as leads to appraise, not settled evidence.
Label any assumed scope as an assumption.
Operating procedure
Order matters: sub-questions must exist before gathering, or the research becomes an unstructured pile shaped by whatever surfaced first.
- Frame. Restate the question and define what a good answer looks like - the form (a number, a ranked list, a causal story) and the bar (how sure it needs to be).
- Map. Decompose into 3-6 sub-questions and research each one, rather than the topic as a blob. If a sub-question splits again, it was two sub-questions.
- Gather. Collect diverse, independent sources per sub-question; prefer primary sources - original data, papers, filings, direct statements - over summaries. Two sources that cite the same origin are one source. Record recency and potential bias for each as you go, not retroactively.
- Cross-check. For each sub-question, mark where sources agree, disagree, or run thin. Disagreement is signal: hypothesize why (different definitions, populations, time periods, incentives) instead of averaging it away.
- Synthesize. Answer the original question with the weight of evidence. Separate evidence from inference and label the inferences. Assign each finding a confidence level: High (multiple independent primary sources agree), Medium (mixed or secondary-heavy support), Low (single source or inference).
- Audit before delivery. Re-check each citation is real and locatable, and that every High-confidence finding actually has the sourcing it claims.
Worked example (findings-table format)
Question: "Is four-day-workweek adoption growing among knowledge-work employers, and what happens to output?"
Sub-question Finding Confidence Sources
Adoption trend Growing from a small base; most Medium Coordinated-trial reports (primary);
employers remain on 5 days national labor-survey data (primary)
Output effect Trials report maintained revenue and Trial-organization data (primary);
lower attrition - but trial firms Medium independent academic follow-up
self-selected, so effects may not
generalize
Who it fails for Thin evidence for client-facing and Low Single practitioner survey; rest is
shift-based work anecdote - GAP: no controlled study foundNote the third row: the honest output is a labeled gap, not a stretched conclusion.
Deliverable
Produce a research brief containing: a summary answering the question in a few sentences up top; findings organized by sub-question, each with citations and a confidence tag; a confidence-and-gaps section stating what is well-supported, what is uncertain, and what is unknown; and a source list with enough detail to locate each item plus a one-line note on its independence and bias.
Do NOT
- Do not invent or embellish a citation - one fabricated source invalidates the entire brief. Never cite something not actually consulted.
- Do not count correlated sources as corroboration; trace what each actually relies on before calling anything consensus.
- Do not average disagreeing sources into a mushy middle. Present the disagreement and the best hypothesis for why it exists.
- Do not let the gathering order set the narrative - the first three sources found are the most findable ones, not the most representative.
- Do not blur evidence and inference. A reader must be able to tell which sentences report sources and which report reasoning.
Quality bar
Before shipping: every sub-question has at least two genuinely independent sources or an explicit gap note; every finding carries a confidence tag consistent with its sourcing; disagreements are surfaced with a hypothesis, not smoothed over; the summary is answerable-from and consistent with the findings; every citation is locatable from the detail given.
Escalation
Route adjacent jobs: designing a study to collect new data is primary-research; compressing an existing corpus of sources into themes and tensions is research-synthesis; a single checkable claim is fact-checker; academic-literature-specific reviews are literature-review or systematic-review. Findings that will drive legal, medical, or financial decisions need professional review before action.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

