Back to Skills

deep-research

Conduct systematic academic literature reviews in 6 phases, producing structured notes, a curated paper database, and a synthesized final report. Output is organized by phase for clarity.

286stars34forksUpdated 8/20/2026

Security Assessment

Safe(92/100)
Security Score92/100

About deep-research

Deep Research conducts systematic academic literature reviews in six strictly sequential phases, producing structured notes, a curated paper database, and a synthesized final report organized by phase. It solves the problem of shallow, abstract-only literature surveys by forcing the agent through frontier discovery, a broad survey, deep reading of full papers, a code-and-tools scan, synthesis, and final report assembly — with a phase-gate protocol that requires the previous phase's output files (with minimum paper/repo counts) to exist on disk before advancing.

The workflow integrates multiple scholarly sources: a conference-paper finder, the arXiv API, the Semantic Scholar Graph API, OpenReview, and ar5iv HTML rendering, with bundled scripts for searching, downloading papers, extracting PDF text, managing BibTeX, maintaining a paper database, and compiling the report. It enforces a paper-quality policy that prioritizes peer-reviewed conference and journal work over preprints and marks preprint status explicitly. Output lands in a per-topic folder structured by phase (frontier, survey, deep dive, code, synthesis, report), and each phase prints a completion checkpoint listing the files it wrote.

Target users are researchers, graduate students, and engineers who need a rigorous, reproducible survey of a technical topic — especially in AI/ML — rather than a quick summary. It is best suited to producing a defensible state-of-the-art review grounded in papers that were actually read, with citations traced to specific findings.

FAQ

What are the six phases?

Frontier discovery, survey, deep dive (reading full papers), code and tools, synthesis, and final report. They must run in strict order 1 through 6, with gate checks verifying each phase's required output files exist before the next begins.

Which sources and APIs does it use?

A conference paper_finder, the arXiv API, the Semantic Scholar Graph API, OpenReview, and ar5iv for HTML paper access, plus direct arXiv PDF download. Bundled scripts handle search, download, PDF extraction, BibTeX, and report compilation.

How does it handle preprints versus peer-reviewed work?

Peer-reviewed conference and journal papers take priority over arXiv preprints. Preprints are used as supplementary evidence, for very recent results, or when no reviewed version exists, and are marked (preprint) in citations.

Do the API integrations need keys?

Semantic Scholar works without a key at 100 requests per 5 minutes, or faster with a key read from a local keys file. arXiv has a conservative rate limit of one request per three seconds. Some bundled paths reference author-specific local paths that may need adjusting for your environment.

Where does output go?

Into a per-topic output folder organized by phase (phase1_frontier, phase2_survey, phase3_deep_dive, phase4_code, phase5_synthesis, and the final report), with a curated paper_db.jsonl database.

All Files

11 files
references/api-reference.md6.1 KB
View
scripts/search_arxiv.py6.5 KB
View
scripts/bibtex_manager.py5.9 KB
View
references/note-format.md4.5 KB
View
scripts/search_semantic_scholar.py11.4 KB
View
references/workflow-phases.md7.6 KB
View
SKILL.md11.3 KB
View
scripts/extract_pdf.py5.8 KB
View
scripts/download_papers.py4.9 KB
View
scripts/compile_report.py9.9 KB
View
scripts/paper_db.py11.1 KB
View

Install deep-research

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill