
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.
- Installs
- 1.9K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/lingzhi227/agent-research-skills --skill deep-research- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads deep-research automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Deep Research Skill
Trigger
Activate this skill when the user wants to:
- "Research a topic", "literature review", "find papers about", "survey papers on"
- "Deep dive into [topic]", "what's the state of the art in [topic]"
- Uses
/research <topic>slash command
Overview
This skill conducts 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.
Installation: ~/.claude/skills/deep-research/ — scripts, references, and this skill definition.
Output: .//Users/lingzhi/Code/deep-research-output/{slug}/ relative to the current working directory.
CRITICAL: Strict Sequential Phase Execution
You MUST execute all 6 phases in strict order: 1 → 2 → 3 → 4 → 5 → 6. NEVER skip any phase.
This is the single most important rule of this skill. Violations include:
- ❌ Jumping from Phase 2 to Phase 5/6 (skipping Deep Dive and Code)
- ❌ Writing synthesis or report before completing Phase 3 deep reading
- ❌ Producing a final report based only on abstracts/titles from search results
- ❌ Combining or merging phases (e.g., doing "Phase 3-5 together")
Phase Gate Protocol
Before starting Phase N+1, you MUST verify that Phase N's required output files exist on disk. If they don't exist, you have NOT completed that phase.
| Phase | Gate: Required Output Files |
|---|---|
| 1 → 2 | phase1_frontier/frontier.md exists AND contains ≥10 papers |
| 2 → 3 | phase2_survey/survey.md exists AND paper_db.jsonl has 35-80 papers |
| 3 → 4 | phase3_deep_dive/selection.md AND phase3_deep_dive/deep_dive.md exist AND deep_dive.md contains detailed notes for ≥8 papers |
| 4 → 5 | phase4_code/code_repos.md exists AND contains ≥3 repositories |
| 5 → 6 | phase5_synthesis/synthesis.md AND phase5_synthesis/gaps.md exist |
After completing each phase, print a phase completion checkpoint:
✅ Phase N complete. Output: [list files written]. Proceeding to Phase N+1.
Why Every Phase Matters
- Phase 3 (Deep Dive) is where you actually READ papers — without it, your synthesis is superficial and based only on abstracts
- Phase 4 (Code & Tools) grounds the research in practical implementations — without it, you miss the open-source ecosystem
- Phase 5 (Synthesis) requires deep knowledge from Phase 3 — you cannot synthesize papers you haven't read
- Phase 6 (Report) assembles content from ALL prior phases — it should cite specific findings from Phase 3 notes
Paper Quality Policy
Peer-reviewed conference papers take priority over arXiv preprints. Many arXiv papers have not undergone peer review and may contain unverified claims.
Source Priority (highest to lowest)
- Top AI conferences: NeurIPS, ICLR, ICML, ACL, EMNLP, NAACL, AAAI, IJCAI, CVPR, KDD, CoRL
- Peer-reviewed journals: JMLR, TACL, Nature, Science, etc.
- Workshop papers: NeurIPS/ICML workshops (lower bar but still reviewed)
- arXiv preprints with high citations: Likely high-quality but unverified
- Recent arXiv preprints: Use cautiously, note "preprint" status explicitly
When to Use arXiv Papers
- As supplementary evidence alongside peer-reviewed work
- For very recent results (< 3 months old) not yet at conferences
- When a peer-reviewed version doesn't exist yet — note
(preprint)in citations - For survey/review papers (these are useful even without peer review)
Search Tools (by priority)
1. paper_finder (primary — conference papers only)
Location: /Users/lingzhi/Code/documents/tool/paper_finder/paper_finder.py
Searches ai-paper-finder.info (HuggingFace Space) for published conference papers. Supports filtering by conference + year. Outputs JSONL with BibTeX.
python /Users/lingzhi/Code/documents/tool/paper_finder/paper_finder.py --mode scrape --config <config.yaml>
python /Users/lingzhi/Code/documents/tool/paper_finder/paper_finder.py --mode download --jsonl <results.jsonl>
python /Users/lingzhi/Code/documents/tool/paper_finder/paper_finder.py --list-venues
Config example:
searches:
- query: "long horizon reasoning agent"
num_results: 100
venues:
neurips: [2024, 2025]
iclr: [2024, 2025, 2026]
icml: [2024, 2025]
output:
root: /Users/lingzhi/Code/deep-research-output/{slug}/phase1_frontier/search_results
overwrite: true
2. search_semantic_scholar.py (supplementary — citation data + broader coverage)
Location: /Users/lingzhi/.claude/skills/deep-research/scripts/search_semantic_scholar.py
Supports --peer-reviewed-only and --top-conferences filters. API key: /Users/lingzhi/Code/keys.md (field S2_API_Key)
3. search_arxiv.py (supplementary — latest preprints)
Location: /Users/lingzhi/.claude/skills/deep-research/scripts/search_arxiv.py
For searching recent papers not yet published at conferences. Mark citations with (preprint).
Other Scripts
| Script | Location | Key Flags |
|---|---|---|
download_papers.py | ~/.claude/skills/deep-research/scripts/ | --jsonl, --output-dir, --max-downloads, --sort-by-citations |
extract_pdf.py | ~/.claude/skills/deep-research/scripts/ | --pdf, --pdf-dir, --output-dir, --sections-only |
paper_db.py | ~/.claude/skills/deep-research/scripts/ | subcommands: merge, search, filter, tag, stats, add, export |
bibtex_manager.py | ~/.claude/skills/deep-research/scripts/ | --jsonl, --output, --keys-only |
compile_report.py | ~/.claude/skills/deep-research/scripts/ | --topic-dir |
WebFetch Mode (no Bash)
- Paper discovery:
WebSearch+WebFetchto query Semantic Scholar/arXiv APIs - Paper reading:
WebFetchon ar5iv HTML orReadtool on downloaded PDFs - Writing:
Writetool for JSONL, notes, report files
6-Phase Workflow
Phase 1: Frontier
Search the latest conference proceedings and preprints to understand current trends.
- Write
phase1_frontier/paper_finder_config.yamltargeting latest 1-2 years - Run paper_finder scrape
- WebSearch for latest accepted paper lists
- Identify trending directions, key breakthroughs
→ Output:
phase1_frontier/frontier.md,phase1_frontier/search_results/
Phase 2: Survey
Build a comprehensive landscape with broader time range. Target 35-80 papers after filtering.
- Write
phase2_survey/paper_finder_config.yamlcovering 2023-2025 - Run paper_finder + Semantic Scholar + arXiv
- Merge all results:
python /Users/lingzhi/.claude/skills/deep-research/scripts/paper_db.py merge - Filter to 35-80 most relevant:
python /Users/lingzhi/.claude/skills/deep-research/scripts/paper_db.py filter --min-score 0.80 --max-papers 70 - Cluster by theme, write survey notes
→ Output:
phase2_survey/survey.md,phase2_survey/search_results/,paper_db.jsonl
Phase 3: Deep Dive ⚠️ DO NOT SKIP
This phase is MANDATORY. You must actually READ 8-15 full papers, not just their abstracts.
- Select 8-15 papers from paper_db.jsonl with rationale → write
phase3_deep_dive/selection.md - Download PDFs:
python download_papers.py --jsonl paper_db.jsonl --output-dir phase3_deep_dive/papers/ --sort-by-citations --max-downloads 15 - For EACH selected paper, read the full text (PDF via
Reador HTML viaWebFetchon ar5iv) - Write detailed structured notes per paper (see note-format.md template): problem, contributions, methodology, experiments, limitations, connections
- Write ALL notes →
phase3_deep_dive/deep_dive.md
Phase 3 Gate: deep_dive.md must contain detailed notes for ≥8 papers, each with methodology and experiment sections filled in. Abstract-only summaries do NOT count.
→ Output: phase3_deep_dive/selection.md, phase3_deep_dive/deep_dive.md, phase3_deep_dive/papers/
Phase 4: Code & Tools ⚠️ DO NOT SKIP
This phase is MANDATORY. You must survey the open-source ecosystem.
- Extract GitHub URLs from papers read in Phase 3
- WebSearch for implementations: "site:github.com {method name}", "site:paperswithcode.com {topic}"
- For each repo found: record URL, stars, language, last updated, documentation quality
- Search for related benchmarks and datasets
- Write →
phase4_code/code_repos.md(must contain ≥3 repositories)
Phase 4 Gate: code_repos.md must exist and contain at least 3 repositories with metadata.
→ Output: phase4_code/code_repos.md
Phase 5: Synthesis (REQUIRES Phase 3 + 4 complete)
Cross-paper analysis. Weight peer-reviewed findings higher. This phase MUST build on the detailed notes from Phase 3 and the code landscape from Phase 4. Taxonomy, comparative tables, gap analysis.
Before starting: Verify phase3_deep_dive/deep_dive.md and phase4_code/code_repos.md exist. If not, go back and complete those phases first.
→ Output: phase5_synthesis/synthesis.md, phase5_synthesis/gaps.md
Phase 6: Compilation (REQUIRES Phase 1-5 complete)
Assemble final report from ALL prior phase outputs. Mark preprint citations with (preprint) suffix.
Before starting: Verify ALL phase outputs exist:
phase1_frontier/frontier.mdphase2_survey/survey.mdphase3_deep_dive/deep_dive.mdphase4_code/code_repos.mdphase5_synthesis/synthesis.md+gaps.md
If ANY are missing, go back and complete the missing phase(s) first.
→ Output: phase6_report/report.md, phase6_report/references.bib
Output Directory
output/{topic-slug}/
├── paper_db.jsonl # Master database (accumulated)
├── phase1_frontier/
│ ├── paper_finder_config.yaml
│ ├── search_results/
│ └── frontier.md
├── phase2_survey/
│ ├── paper_finder_config.yaml
│ ├── search_results/
│ └── survey.md
├── phase3_deep_dive/
│ ├── papers/
│ ├── selection.md
│ └── deep_dive.md
├── phase4_code/
│ └── code_repos.md
├── phase5_synthesis/
│ ├── synthesis.md
│ └── gaps.md
└── phase6_report/
├── report.md
└── references.bib
Key Conventions
- Paper IDs: Use
arxiv_idwhen available, otherwise Semantic ScholarpaperId - Citations:
[@key]format, key = firstAuthorYearWord (e.g.,[@vaswani2017attention]) - JSONL schema: title, authors, abstract, year, venue, venue_normalized, peer_reviewed, citationCount, paperId, arxiv_id, pdf_url, tags, source
- Preprint marking: Always note
(preprint)when citing non-peer-reviewed work - Incremental saves: Each phase writes to disk immediately
- Paper count: Target 35-80 papers in final paper_db.jsonl (use
paper_db.py filter)
References
/Users/lingzhi/.claude/skills/deep-research/references/workflow-phases.md— Detailed 6-phase methodology/Users/lingzhi/.claude/skills/deep-research/references/note-format.md— Note templates, BibTeX format, report structure/Users/lingzhi/.claude/skills/deep-research/references/api-reference.md— arXiv, Semantic Scholar, ar5iv API guide
Related Skills
- Downstream: literature-search, literature-review, citation-management
- See also: novelty-assessment, survey-generation
FAQ
What does the deep-research skill do?
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.
How do I install deep-research?
Run npx skills add https://github.com/lingzhi227/agent-research-skills --skill deep-research in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/deep-research/ (personal) or .claude/skills/deep-research/ (project).
Which AI agents can use deep-research?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is deep-research safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains deep-research?
It is published by lingzhi227 in lingzhi227/agent-research-skills. It has 1,897 recorded installs.
More from lingzhi227/agent-research-skills
literature-review
lingzhi227/agent-research-skills
Conduct comprehensive literature reviews using multi-perspective dialogue simulation. Generate diverse expert personas, conduct grounded Q&A conversations, and synthesize findings into structured knowledge. Use when starting a new research project or writing a survey section.
literature-search
lingzhi227/agent-research-skills
Search academic literature using Semantic Scholar, arXiv, and OpenAlex APIs. Returns structured JSONL with title, authors, year, venue, abstract, citations, and BibTeX. Use when the user needs to find papers, check related work, or build a bibliography.
figure-generation
lingzhi227/agent-research-skills
Generate publication-quality scientific figures using matplotlib/seaborn with a three-phase pipeline (query expansion, code generation with execution, VLM visual feedback). Handles bar charts, line plots, heatmaps, training curves, ablation plots, and more. Use when the user needs figures, plots, or visualizations for a paper.
latex-formatting
lingzhi227/agent-research-skills
Handle LaTeX formatting, templates, and styling for academic papers. Set up conference templates (ICML, ICLR, NeurIPS, AAAI, ACL), fix formatting issues, manage packages, and ensure venue-specific compliance. Use when the user needs to set up a paper template, fix LaTeX formatting, or prepare for submission.
math-reasoning
lingzhi227/agent-research-skills
Formal mathematical reasoning for research papers — derive equations, write proofs, formalize problem settings, select statistical tests, and generate LaTeX math notation. Use when the user needs mathematical derivations, theorem proofs, notation tables, or statistical analysis formalization.
backward-traceability
lingzhi227/agent-research-skills
Make every number in the final PDF traceable to the exact code line that produced it. Uses \hypertarget/\hyperlink LaTeX commands and \num{formula} evaluated at compile time. Use for reproducibility and data integrity verification.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。