agentleFS
rongarederongarede/claude-skills-research/skills/deep-research/SKILL.md

deep-research

Skill3 starsChanged 8 months agoMITView on GitHub

Generate format-controlled research reports with evidence tracking, citations, and iterative review. This skill should be used when users request a research report, literature review, market or industry analysis, competitive landscape, policy or technical brief, or require a strict report template and section formatting that a single deepresearch pass cannot reliably enforce.

  • Pipes a download into a shell

196 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

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.
  • nicepkgSkill

    community-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

  • nicepkgSkill

    ph-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-MoorerSkill

    academic-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-MoorerSkill

    academic-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

  • xfstudioSkill

    micro-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

  • stophobiaSkill

    surprise-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

The file

Show its rules and text

We split this skill into the rules it gives an agent

25 rules. 0 are common, 24 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 24

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create high-fidelity research reports with strict format control, evidence mapping, and multi-pass synthesis.

    line 9
  2. Distinctive:

    Ask for any existing style guide or sample report

    line 53
  3. Distinctive:

    Create a concise report spec file:

    line 55
  4. Distinctive:

    If a user provides a template or an example report, treat it as a hard constraint and mirror the structure.

    line 74
  5. Distinctive:

    Use references/research_plan_checklist.md for guidance.

    line 86
  6. Distinctive:

    Use the deepresearch tool to collect evidence and citations.

    line 90
  7. Distinctive:

    Run multiple complete passes if coverage is uncertain

    line 92
  8. Distinctive:

    After all agents complete, merge raw files using UNION (Step 4)

    line 109
  9. Distinctive:

    Never run a single agent for all dimensions when parallel execution is possible

    line 110
  10. Distinctive:

    If deepresearch is unavailable, rely on user-provided sources only and state limitations explicitly.

    line 120
  11. Distinctive:

    After evidence collection, download source PDFs for full-text extraction:

    line 124
  12. Very specific:

    Create download_log.md with success/failure tracking

    line 138
  13. Distinctive:

    Read downloaded PDFs and extract paragraphs matching research keywords:

    line 172
  14. Distinctive:

    Search for keyword matches: extract the full surrounding paragraph (at least 3 sentences of context)

    line 178
  15. Distinctive:

    Create an outline that enforces the format contract:

    line 200
  16. Distinctive:

    Use the template in references/research_report_template.md

    line 202
  17. Distinctive:

    Avoid single-pass drafting.

    line 208
  18. Distinctive:

    Use the Task tool to spawn parallel subagents with isolated context.

    line 212
  19. Distinctive:

    Keep all unique findings from all versions

    line 236
  20. Distinctive:

    Ensure every claim in the merged draft has a cited source

    line 238
  21. Distinctive:

    Every numeric claim has at least one source

    line 246
  22. Distinctive:

    Every recommendation references supporting evidence

    line 247
  23. Distinctive:

    No orphan claims without citations

    line 248
  24. Distinctive:

    Use references/completeness_review_checklist.md.

    line 252
  25. Distinctive:

    If the user provides another AI output, cross-compare and UNION merge

    line 260

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deep Research

Create high-fidelity research reports with strict format control, evidence mapping, and multi-pass synthesis.

Quick Start

  1. Clarify the report spec and format contract
  2. Build a research plan and query set
  3. Collect evidence with parallel agents (multi-source) 3.5. Download source PDFs (arXiv + sci-hub)
  4. Triage sources and build an evidence table 4.5. Extract paragraphs from downloaded PDFs
  5. Outline and section map
  6. Multi-pass full drafting (parallel subagents)
  7. UNION merge, enforce format compliance, verify citations
  8. Evidence and citation verification
  9. Present draft for human review and iterate

Core Workflow

Copy this checklist and track progress:

Deep Research Progress:
- [ ] Step 1: Intake and format contract
- [ ] Step 2: Research plan and query set
- [ ] Step 3: Evidence collection (parallel agents)
- [ ] Step 3.5: PDF download (arXiv + sci-hub)
- [ ] Step 4: Source triage and evidence table
- [ ] Step 4.5: PDF paragraph extraction
- [ ] Step 5: Outline and section map
- [ ] Step 6: Multi-pass full drafting (parallel subagents)
- [ ] Step 7: UNION merge and format compliance
- [ ] Step 8: Evidence and citation verification
- [ ] Step 9: Present draft for human review and iterate

Step 1: Intake and Format Contract

Establish the report requirements before any research:

  • Confirm audience, purpose, scope, time range, and geography
  • Lock output format: Markdown, DOCX, slides, or user-provided template
  • Capture required sections and exact formatting rules
  • Confirm citation style (footnotes, inline, numbered, APA, etc.)
  • Confirm length targets per section
  • Ask for any existing style guide or sample report

Create a concise report spec file:

Report Spec:
- Audience:
- Purpose:
- Scope:
- Time Range:
- Geography:
- Required Sections:
- Section Formatting Rules:
- Citation Style:
- Output Format:
- Length Targets:
- Tone:
- Must-Include Sources:
- Must-Exclude Topics:

If a user provides a template or an example report, treat it as a hard constraint and mirror the structure.

Step 2: Research Plan and Query Set

Define the research strategy before calling tools:

  • Break the main question into 3-7 subquestions
  • Define key entities, keywords, and synonyms
  • Identify primary sources vs secondary sources
  • Define disqualifiers (outdated, low quality, opinion-only)
  • Assemble a query set per section

Use references/research_plan_checklist.md for guidance.

Step 3: Evidence Collection (Deepresearch Tool)

Use the deepresearch tool to collect evidence and citations.

  • Run multiple complete passes if coverage is uncertain
  • Vary query phrasing to reduce blind spots
  • Preserve raw tool output in files for traceability

Parallel Evidence Collection (Academic Research)

For academic literature searches, split evidence collection across multiple parallel agents by data source:

AgentData SourceTool
Agent 1Semantic Scholarsemantic-scholar skill API
Agent 2arXiv preprintsarxiv-search skill + WebSearch site:arxiv.org
Agent 3IEEE/ACM + Chinese databasesWebSearch site:ieeexplore.ieee.org + Chinese keywords

Execution rules:

  • Launch all agents simultaneously with run_in_background=true
  • Each agent writes to a separate raw output file (e.g., raw_S2.md, raw_arXiv.md, raw_IEEE.md)
  • After all agents complete, merge raw files using UNION (Step 4)
  • Never run a single agent for all dimensions when parallel execution is possible

File structure (recommended):

<output_dir>/research/<topic-name>/
  deepresearch_pass1.md
  deepresearch_pass2.md
  deepresearch_pass3.md

If deepresearch is unavailable, rely on user-provided sources only and state limitations explicitly.

Step 3.5: PDF Download (Academic Research)

After evidence collection, download source PDFs for full-text extraction:

Download routes (in priority order):

Source TypeDownload MethodTool
arXiv papersDirect curl: https://arxiv.org/pdf/{id}.pdfBash with proxy
DOI paperssci-hub-download skill (OA → Sci-Hub → publisher)sci-hub-download skill
Chinese papersManual download requiredFlag for user

Execution:

  • Extract arXiv IDs and DOIs from evidence collection outputs using Grep
  • Launch 2 parallel download agents: one for arXiv (curl), one for DOI (sci-hub)
  • Save all PDFs to <output_dir>/research/papers/
  • Create download_log.md with success/failure tracking
  • Validate downloads: PDF files must be >100KB to be considered valid

File structure:

<output_dir>/research/papers/
  paper1.pdf
  paper2.pdf
  ...
  download_log.md

This step is MANDATORY for academic research tasks. Do not skip to Step 4 without downloading available PDFs.

Step 4: Source Triage and Evidence Table

Normalize and score sources before drafting:

  • De-duplicate sources across passes
  • Score sources using references/source_quality_rubric.md
  • Build an evidence table mapping claims to sources

Evidence table minimum columns:

  • Source ID
  • Title
  • Publisher
  • Date
  • URL or reference
  • Quality tier (A/B/C)
  • Notes

Step 4.5: PDF Paragraph Extraction (Academic Research)

Read downloaded PDFs and extract paragraphs matching research keywords:

Execution:

  • Split PDFs into batches of ~10 by filename alphabetical order
  • Launch parallel reader agents (one per batch) with run_in_background=true
  • Each reader uses the Read tool with pages parameter to read PDFs in 20-page chunks
  • Search for keyword matches: extract the full surrounding paragraph (at least 3 sentences of context)
  • Record: page number, section heading, full paragraph text

Output format per paper:

### [filename] Paper Title
#### Page X — Section Heading
> Extracted paragraph text...

Write extracted paragraphs to:

<output_dir>/research/extracts/
  batch1.md
  batch2.md
  ...

These raw extracts feed into Step 5 (outline) and Step 6 (drafting) as primary evidence.

Step 5: Outline and Section Map

Create an outline that enforces the format contract:

  • Use the template in references/research_report_template.md
  • Produce a section map with required elements per section
  • Confirm ordering and headings match the report spec

Step 6: Multi-Pass Full Drafting (Parallel Subagents)

Avoid single-pass drafting; generate multiple complete reports, then merge.

Preferred Strategy: Parallel Subagents (Complete Draft Each)

Use the Task tool to spawn parallel subagents with isolated context. Each subagent must:

  • Load the report spec, outline, and evidence table
  • Draft the FULL report (all sections)
  • Enforce formatting rules and citation style

Implementation pattern:

Task(subagent_type="general-purpose", prompt="Draft complete report ...", run_in_background=false) -> version1.md
Task(subagent_type="general-purpose", prompt="Draft complete report ...", run_in_background=false) -> version2.md
Task(subagent_type="general-purpose", prompt="Draft complete report ...", run_in_background=false) -> version3.md

Write drafts to files, not conversation context:

<output_dir>/intermediate/<topic-name>/version1.md
<output_dir>/intermediate/<topic-name>/version2.md
<output_dir>/intermediate/<topic-name>/version3.md

Step 7: UNION Merge and Format Compliance

Merge using UNION, never remove content without evidence-based justification:

  • Keep all unique findings from all versions
  • Consolidate duplicates while preserving the most detailed phrasing
  • Ensure every claim in the merged draft has a cited source
  • Enforce the exact section order, headings, and formatting
  • Re-run formatting rules from references/formatting_rules.md

Step 8: Evidence and Citation Verification

Verify traceability:

  • Every numeric claim has at least one source
  • Every recommendation references supporting evidence
  • No orphan claims without citations
  • Dates and time ranges are consistent
  • Conflicts are explicitly called out with both sources

Use references/completeness_review_checklist.md.

Step 9: Present Draft for Human Review and Iterate

Present the draft as a reviewable version:

  • Emphasize that format compliance and factual accuracy need human review
  • Accept edits to format, structure, and scope
  • If the user provides another AI output, cross-compare and UNION merge

Output Requirements

  • Match the requested language and tone
  • Preserve technical terms in English
  • Respect the report spec and formatting rules
  • Include a references section or bibliography

Reference Files

FileWhen to Load
research_report_template.mdBuild outline and draft structure
formatting_rules.mdEnforce section formatting and citation rules
source_quality_rubric.mdScore and triage sources
research_plan_checklist.mdBuild research plan and query set
completeness_review_checklist.mdReview for coverage, citations, and compliance

Anti-Patterns

  • Single-pass drafting without parallel complete passes
  • Splitting passes by section instead of full report drafts
  • Ignoring the format contract or user template
  • Claims without citations or evidence table mapping
  • Mixing conflicting dates without calling out discrepancies
  • Copying external AI output without verification
  • Deleting intermediate drafts or raw research outputs
  • Running a single search agent when multiple data sources are available
  • Skipping PDF download and relying only on search snippets/abstracts
  • Sequential evidence collection when parallel execution is possible
  • Waiting for user prompts between steps instead of pipeline execution

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.