academic-deep-research
Use when evaluating academic papers or surveying a research topic. Gathers venue, citations, GitHub stats, social buzz, reproducibility, and author signals to produce a scored markdown report. Triggers: "evaluate paper", "paper review", "research survey", "literature review", "is this paper good", "find papers on", "compare papers", "paper impact"
Best use case
academic-deep-research is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when evaluating academic papers or surveying a research topic. Gathers venue, citations, GitHub stats, social buzz, reproducibility, and author signals to produce a scored markdown report. Triggers: "evaluate paper", "paper review", "research survey", "literature review", "is this paper good", "find papers on", "compare papers", "paper impact"
Teams using academic-deep-research should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/academic-deep-research/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How academic-deep-research Compares
| Feature / Agent | academic-deep-research | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when evaluating academic papers or surveying a research topic. Gathers venue, citations, GitHub stats, social buzz, reproducibility, and author signals to produce a scored markdown report. Triggers: "evaluate paper", "paper review", "research survey", "literature review", "is this paper good", "find papers on", "compare papers", "paper impact"
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Academic Deep Research
## When to Use
- Evaluating a single paper (given arxiv URL, title, or DOI)
- Surveying a research topic and ranking papers by quality/impact
- Deciding whether to read, cite, or build on a paper
- Comparing multiple papers in a research area
## Two Workflows
### Single Paper Mode
Input: arxiv URL, paper title, or DOI.
- [ ] **Extract metadata** — title, authors, date, abstract from arxiv or Semantic Scholar
- [ ] **Query citations + venue** — Semantic Scholar API
- [ ] **Find GitHub repo** — Papers With Code → paper page → WebSearch fallback chain
- [ ] **Gather code health** — `gh api` for stars, forks, last push, open issues
- [ ] **Check reproducibility** — HuggingFace models/datasets, third-party reimplementations
- [ ] **Search social buzz** — Twitter/X, Reddit, HackerNews via WebSearch
- [ ] **Score all 8 dimensions** — apply scoring rubric below
- [ ] **Write report** — save to `docs/research/YYYY-MM-DD-<paper-slug>.md`
### Topic Survey Mode
Input: research topic or question.
- [ ] **Find candidate papers** — WebSearch + Semantic Scholar, collect 5-15 papers
- [ ] **Evaluate each paper** — run Single Paper Mode per paper (parallelize via subagents)
- [ ] **Rank by composite score** — descending
- [ ] **Write report** — ranked table + per-paper scorecards to `docs/research/YYYY-MM-DD-<topic-slug>-survey.md`
## Scoring Rubric (8 Dimensions, 0-20)
### 1. Venue (0-3)
| Score | Criteria |
|-------|----------|
| 3 | Top-tier oral/spotlight (NeurIPS, ICML, ICLR, CVPR, ICCV, ECCV, ACL, EMNLP, SIGGRAPH, JMLR, TPAMI) |
| 2 | Top-tier poster/accepted |
| 1 | Workshop, second-tier venue (AAAI, WACV, BMVC, COLING), or journal under review |
| 0 | Arxiv-only, no peer review |
### 2. Citations (0-3)
Normalized by paper age (citations per month since publication):
| Score | Criteria |
|-------|----------|
| 3 | >10 citations/month |
| 2 | 3-10 citations/month |
| 1 | 0.5-3 citations/month |
| 0 | <0.5 citations/month |
### 3. Code Available (0-1)
Binary. 1 = official repo exists. 0 = no code released.
### 4. Code Health (0-3)
Only scored if code exists:
| Score | Criteria |
|-------|----------|
| 3 | >1k stars AND last push <30 days |
| 2 | >200 stars OR (>50 stars AND last push <30 days) |
| 1 | Repo exists, <200 stars, last push <6 months |
| 0 | Repo abandoned (last push >6 months) or no repo |
### 5. Reproducibility (0-3)
| Score | Criteria |
|-------|----------|
| 3 | HuggingFace models/datasets + third-party reimplementations |
| 2 | Either HF presence OR third-party reimplementation |
| 1 | Official code runs, but no third-party adoption |
| 0 | No code, no reproductions |
### 6. Social Buzz (0-3)
| Score | Criteria |
|-------|----------|
| 3 | Viral — multiple platforms, >200 likes/upvotes total |
| 2 | Notable — discussed on 1-2 platforms, moderate engagement |
| 1 | Mentioned — a few tweets or a Reddit thread |
| 0 | No detectable discussion |
### 7. Recency (0-2)
| Score | Criteria |
|-------|----------|
| 2 | Published within last 12 months |
| 1 | 1-3 years old |
| 0 | >3 years old |
### 8. Author Signal (0-2)
| Score | Criteria |
|-------|----------|
| 2 | Top lab (FAIR, DeepMind, OpenAI, MSR, etc.) OR first/last author h-index >40 |
| 1 | Known university group OR h-index 15-40 |
| 0 | Unknown affiliation, early-career authors |
### Composite Tiers
| Score | Tier |
|-------|------|
| 16-20 | Landmark paper |
| 11-15 | Strong paper |
| 6-10 | Solid paper |
| 0-5 | Early/niche/weak signal |
## Data Gathering Commands
### Semantic Scholar (citations, venue, authors)
```
WebFetch → https://api.semanticscholar.org/graph/v1/paper/arXiv:{id}?fields=title,year,venue,citationCount,authors,externalIds,publicationVenue,publicationTypes
```
For title search:
```
WebFetch → https://api.semanticscholar.org/graph/v1/paper/search?query={url_encoded_title}&limit=5&fields=title,year,venue,citationCount,authors,externalIds,publicationVenue
```
### GitHub Stats
```bash
gh api repos/{owner}/{repo} --jq '{stars: .stargazers_count, forks: .forks_count, last_push: .pushed_at, open_issues: .open_issues_count}'
```
### Repo Discovery Fallback Chain
Try in order until a repo is found:
1. `WebSearch → "{paper title} site:paperswithcode.com"` — check the Papers With Code page for linked repos
2. `WebFetch` the arxiv abstract page — look for GitHub links in the abstract or comments
3. `WebSearch → "{paper title} github"` — direct search
4. `WebSearch → "{first author name} {method name} github"` — author-based search
### Social Buzz
```
WebSearch → "{paper title}" AND (site:x.com OR site:twitter.com OR site:reddit.com OR site:news.ycombinator.com)
```
If no results, broaden:
```
WebSearch → "{method name} {first author last name}" AND (twitter OR reddit OR "hacker news")
```
### HuggingFace Adoption
```
WebSearch → "{method name}" site:huggingface.co
```
### Topic Survey — Paper Discovery
```
WebSearch → "{topic} survey OR benchmark OR state-of-the-art 2024 2025"
WebFetch → https://api.semanticscholar.org/graph/v1/paper/search?query={topic}&limit=20&fields=title,year,venue,citationCount,authors&sort=citationCount:desc
```
## Report Templates
### Single Paper Report
```markdown
# Paper Evaluation: <Title>
**Date**: YYYY-MM-DD
**Paper**: <arxiv link>
**Authors**: <author list>
**Venue**: <conference/journal or "arxiv preprint">
## Scorecard
| Dimension | Score | Detail |
|-----------------|-------|-------------------------------------|
| Venue | _/3 | |
| Citations | _/3 | |
| Code Available | _/1 | |
| Code Health | _/3 | |
| Reproducibility | _/3 | |
| Social Buzz | _/3 | |
| Recency | _/2 | |
| Author Signal | _/2 | |
| **Total** | **_/20** | **<tier>** |
## Key Findings
- <2-3 bullet summary of contributions>
## Code & Reproducibility
- Repo: <link> | Stars: X | Forks: X | Last push: X
- HuggingFace: <models/datasets if any>
- Third-party implementations: <links if any>
## Social Discussion
- <Notable tweets, Reddit threads, HN posts with links>
## Verdict
<1-2 sentence recommendation: worth reading/implementing/citing?>
```
### Topic Survey Report
```markdown
# Topic Survey: <Topic>
**Date**: YYYY-MM-DD
**Papers evaluated**: N
## Ranked Papers
| Rank | Paper | Venue | Score | Stars | Citations |
|------|-------|-------|-------|-------|-----------|
| 1 | ... | ... | _/20 | ... | ... |
## Per-Paper Evaluations
<individual scorecards>
```
## Anti-Patterns
- **Scoring without data**: Never assign a score based on assumption. If a data source is unreachable, mark as "N/A" and note it. Do not guess.
- **Stars as sole proxy for quality**: A viral repo with 10k stars may have no peer review. Stars measure popularity, not correctness. Always cross-check with venue and citations.
- **Ignoring negative signals**: An abandoned repo (last push >1 year), retracted paper, or controversy in discussions are important findings. Report them prominently.
- **Recency bias**: A 3-year-old paper with 2000 citations is more impactful than a 1-month-old paper with 5 stars. Recency is one signal, not the signal.
- **Skipping social search**: Social discussion often surfaces limitations, failed reproductions, and real-world usage that papers don't mention.
- **Over-weighting author prestige**: A paper from an unknown lab that ships working code and gets adopted beats a famous-lab paper with no code release.
## See Also
- `ml-ablation-design` — Evaluating experimental rigor within papers
- `genai-evaluation-metrics` — Understanding evaluation metrics referenced in papers
- `fail-fast-ml-engineering` — Assessing code quality of released implementations
- `arxiv-latex-reader` — Progressive reading of large arxiv papers without context overflow
- `idea-explore` — Invokes this skill for adjacent-literature angles when proposing new directions anchored to a seed paperRelated Skills
ml-ablation-design
Use when designing ablation studies to compare model components, loss functions, or architectural choices. Covers synthetic data experiments, variant loops, production metrics, and W&B grouping. Triggers: "ablation", "ablation study", "variant comparison", "controlled experiment", "synthetic data experiment"
gpu-training-acceleration
Use when optimizing PyTorch training speed or memory on CUDA GPUs — global flags, torch.compile, fused optimizers, mixed precision, gradient checkpointing, kernel fusion, memory layout, or latent-space training. Applies to any PyTorch training workload. Triggers: "torch.compile", "TF32", "fused optimizer", "mixed precision", "bf16", "fp16", "gradient checkpointing", "Triton kernel", "CUDA flags", "GPU slow", "GPU memory"
genai-evaluation-metrics
Use when evaluating generative models — choosing metrics (FID, IS, KID, sFID, FDD, FVD, PRDC, LPIPS, SSIM, AuthPct, Vendi), setting up online or offline evaluation, feature extractor selection, distributed computation, memory management during sampling. Triggers: "FID", "IS", "KID", "inception score", "frechet", "LPIPS", "SSIM", "evaluation metrics", "generative evaluation", "FVD"
youtube-wiki
Use when reading a YouTube video (especially an AI/ML interview, podcast, or technical talk) and producing a faithful, timestamped wiki entry the user can return to weeks later. Fetches the transcript via yt-dlp, sections by chapters or LLM-detected topics, summarizes per-section with parallel subagents, preserves verbatim quotes with speaker attribution, and runs a coverage test against the raw transcript. Triggers: "youtube wiki", "video wiki", "summarize this youtube", "watch this interview", "read this talk", "digest this video", "https://youtu.be/", "https://www.youtube.com/watch"
pdf-reader
Use when reading PDF papers, reports, or long documents where text, figures, and tables must all be captured and chunk-summarized without truncation. Converts PDF to a markdown + paper_content.json workspace, extracts figures and tables as standalone files, then delegates to arxiv-latex-reader's progressive two-layer reading (section index + on-demand deep reads). Triggers: "read pdf", "pdf to markdown", "summarize pdf", "pdf paper", "extract figures from pdf", "extract tables from pdf", "marker pdf", "pymupdf", "docling", "paper digest", "pdf reader"
insert-wiki
Use when capturing a single URL (X tweet, LinkedIn post, HN thread, short blog, news article, GitHub gist or issue) as a small persistent markdown entry the user can re-read later for motivation or grep across future sessions. Verbatim body + author + tags + a one-line "Why I saved this" hook. Writes to docs/wikis/YYYY-MM-DD-<slug>.md. WebFetch by default; CDP via Playwright MCP for login-walled hosts (x.com, twitter.com, linkedin.com). Redirects YouTube / arXiv / GitHub repo URLs to their specialized skills. Triggers: "insert wiki", "add to wiki", "insert this", "save this tweet", "capture this post", "add this to my wiki", "remember this link", "https://x.com/", "https://twitter.com/", "https://linkedin.com/posts/"
idea-feasibility
Use when evaluating whether a research or product idea is actually feasible — buildable, evaluable, and de-risked by available checkpoints, code, datasets, and GPU budget. Normalizes the idea, gathers primary-source evidence (arXiv, GitHub, project pages, model hosts), scores it against four mandatory hard gates, and emits a verdict + falsifiable MVP. Triggers: "idea feasibility", "is this idea feasible", "feasibility check", "can we do this", "is this practical", "worth pursuing", "评估想法可行性", "可行性分析", "这个 idea 能做吗", "这个想法靠谱吗"
idea-explore
Use when proposing new research ideas grounded in a seed paper or method — surfaces the gaps that the citation cone hasn't filled, the drawbacks the community already complains about in the official repo's GitHub issues, and the adjacent angles the literature suggests. Orchestrates followup-analysis (already-done exclusion), GitHub-issue mining (known drawbacks), and academic-deep-research (adjacent literature) into a ranked candidate-ideas report. Triggers: "idea explore", "idea-explore", "propose ideas", "explore ideas", "new directions", "research gaps", "what's missing", "build on this paper", "探索想法", "提出新想法", "研究空白"
idea-box
Use when promoting an idea from a fleeting thought into a tracked artifact with a lifecycle. Defines a per-idea on-disk directory (./idea_box/<slug>/) and a hard-gated state machine (explored → feasible/blocked → building → built/killed) that the existing reader/evaluator skills (idea-feasibility, ml-ablation-design, academic-deep-research, followup-analysis, arxiv-latex-reader, pdf-reader, github-reader, blog-reader) plug into. Public repo ships only the convention; idea data lives in the user's private idea-box repo. Triggers: "idea box", "idea-box", "new idea", "advance idea", "list ideas", "kill idea", "想法箱", "新想法", "推进想法", "列出想法"
github-reader
Use when reading a GitHub repository (especially a research code release with an accompanying paper) and producing a faithful digest that covers the implementation logic, the main insight, and the key reported results. Research-first with graceful fallback for non-paper repos. Handles arXiv link detection and delegates paper reading to arxiv-latex-reader / pdf-reader. Triggers: "read repo", "read this github", "analyze github", "digest repo", "github reader", "extract from github", "summarize this codebase", "read this code", "https://github.com/"
blog-reader
Use when reading a long technical blog post (ML research, engineering deep-dives, Distill/Lil'Log-style posts) and producing a faithful, figure-aware summary. Handles context-over-limit via section-based chunking, captures important figures via multimodal Read, and runs a coverage test to catch missing information. Triggers: "read this blog", "summarize this post", "read blog", "digest this article", "long blog post", "read this article", "blog summary", "distill post", "summarize url", "chunk and summarize"
arxiv-latex-reader
Use when reading large arxiv papers without context overflow. Progressive two-layer reading: index all sections (~2k tokens), then deep-read on demand. Never truncates. Triggers: "read paper", "paper sections", "section index", "progressive reading", "paper_content.json", "section summary"