Agent skill

Literature Review

by Mathews-Tom in Mathews-Tom/armory

Systematic literature review workflow: scope, search (arXiv, Semantic Scholar, Google Scholar), screen, extract, synthesize, and identify gaps.

MITAuto-check passedResearch & Science

Install Literature Review

skills CLI
$ npx skills add Mathews-Tom/armory --skill literature-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Mathews-Tom/armory literature-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/literature-review .claude/skills/literature-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
literature-review
GitHub stars
329
Token cost
~2.6k tokens
SKILL.md length
1,019 words
Files
5 (incl. references)
Skills in repo
80
Repo updated
First seen
Licence
MIT

At a glance

Systematic literature review workflow: scope, search (arXiv, Semantic Scholar, Google Scholar), screen, extract, synthesize, and identify gaps.

  • Works in 6 steps: Scope Definition → Search & Discovery → Screening & Filtering → …
  • : literature review
  • SKILL.md covers When to use this skill vs.…, Workflow, Quality Checks and Edge Cases
  • Calls uv; reaches api.semanticscholar.org and connectedpapers.com

What it does

Literature Review is an agent skill from Mathews-Tom/armory. Systematic literature review workflow: scope, search (arXiv, Semantic Scholar, Google Scholar), screen, extract, synthesize, and identify gaps. Triggers on: "literature review", "survey the literature", "related work", "systematic review", "synthesize the research", "find papers about", "research gap analysis".

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `evals/cases.yaml`, `references/citation-formats.md` and `references/search-strategy.md`).

It sits in Research & Science, covering Literature review and Academic paper search. It works with arXiv and Semantic Scholar. The repository describes itself as: Curated, production-grade skills for AI coding agents. Battle-tested workflows for developers who use AI seriously. The licence is MIT.

When your agent uses it

  • : literature review
  • Survey the literature
  • Systematic review
  • Synthesize the research

Example prompts

  • “literature review”
  • “survey the literature”
  • “related work”
  • “/literature-review”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Scope Definition
  2. Search & Discovery
  3. Screening & Filtering
  4. Data Extraction
  5. Synthesis
  6. Output

What it can do on your machine

Read from SKILL.md and the folder at commit 4594fb7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.semanticscholar.org
    • connectedpapers.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Literature Review loads about 2.6k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 1,019 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Mathews-Tom/armory at commit 4594fb7, republished under its MIT licence (© Mathews-Tom). 1,019 words, ~2,592 tokens.

Download SKILL.mdSave it as .claude/skills/literature-review/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
literature-review
description
Systematic literature review workflow: scope, search (arXiv, Semantic Scholar, Google Scholar), screen, extract, synthesize, and identify gaps. Triggers on: "literature review", "survey the literature", "related work", "systematic review", "synthesize the research", "find papers about", "research gap analysis".
metadata.version
1.0.1
metadata.complements
arxiv-search, research-critique, manuscript-review, manuscript-provenance
metadata.category
review
metadata.tags
academic, literature, synthesis, citations
metadata.difficulty
intermediate

Literature Review

Systematic discovery, extraction, and synthesis of academic research on a defined topic.

When to use this skill vs. others

NeedSkill
Survey a research area, synthesize multiple papersliterature-review (this skill)
Critique a single paper's methodology and claimsresearch-critique
Audit a manuscript's formatting, structure, citationsmanuscript-review
Verify a manuscript's numbers trace to codemanuscript-provenance
Search arXiv for papers matching a queryarxiv-search (utility)

Workflow

Phase 1: Scope Definition

Before searching, establish the review boundaries:

  1. Research question — What specific question does the review answer? Vague topics produce vague reviews. "What techniques exist for X" is weaker than "How do methods for X compare on metric Y across domains Z?"
  2. Inclusion criteria — Define what counts:
    • Date range (e.g., 2020–present)
    • Publication type (peer-reviewed, preprints, both)
    • Domains/categories (e.g., cs.CL, cs.AI)
    • Minimum relevance threshold
  3. Exclusion criteria — Define what does not count:
    • Tangentially related work
    • Non-primary sources (blog posts, tutorials) unless explicitly included
    • Duplicate or superseded versions
  4. Expected output — What form should the review take? Narrative synthesis, tabular comparison, gap analysis, annotated bibliography, or related-work section?

Present the scope to the user for confirmation before proceeding.

Phase 2: Search & Discovery

Execute searches across available sources. Use multiple queries with varying specificity to avoid single-query blind spots.

Primary source: arXiv (via arxiv-search utility)

bash
uv run --with arxiv python scripts/arxiv_search.py "QUERY" --max-results 30 --sort-by relevance

Vary queries systematically:

  • Broad topic query: "retrieval augmented generation"
  • Field-scoped query: ti:retrieval AND abs:generation AND cat:cs.CL
  • Author-anchored query: au:lewis AND abs:retrieval (when key authors are known)
  • Recency query: same terms with --sort-by submitted

Secondary sources (via web search/fetch):

  • Semantic Scholar API: https://api.semanticscholar.org/graph/v1/paper/search?query=QUERY&limit=20&fields=title,authors,abstract,year,citationCount,externalIds
  • Google Scholar (via web search): site:scholar.google.com QUERY
  • Connected Papers (for citation graph exploration): https://www.connectedpapers.com/search?q=QUERY

Snowball strategy:

  • Forward snowball: find papers that cite a key paper (Semantic Scholar citations endpoint)
  • Backward snowball: follow the references of key papers
  • Use citation count as a signal for influence, not quality
Phase 3: Screening & Filtering

For each discovered paper, apply the inclusion/exclusion criteria from Phase 1.

Produce a screening table:

#IDTitleAuthorsYearRelevant?Reason
12301.07041Paper TitleAuthor et al.2023YesDirectly addresses RQ
22302.12345Other PaperAuthor B2023NoTangential — focuses on X not Y

Rules:

  • Screen on title + abstract first. Read full paper only for borderline cases.
  • When uncertain, include. It is cheaper to drop a paper later than to miss it.
  • Track exclusion reasons — they inform the review's limitations section.
  • Flag papers that appear in multiple search queries as likely high-relevance.
Phase 4: Data Extraction

For each included paper, extract a structured record:

yaml
- id: "2301.07041"
  title: "Paper Title"
  authors: ["Author One", "Author Two"]
  year: 2023
  venue: "NeurIPS 2023"
  research_question: "How does X affect Y?"
  methodology: "Controlled experiment with N=1000"
  key_findings:
    - "Finding 1 with quantitative result"
    - "Finding 2 with effect size"
  limitations: "Single-domain evaluation"
  relevance_to_rq: "Directly compares methods A and B on metric Y"
  citation_count: 142

Extraction discipline:

  • Record what the paper demonstrates, not what it claims to demonstrate.
  • Distinguish empirical findings (data-backed) from interpretive claims (author's framing).
  • Note methodology details that enable cross-paper comparison (datasets, metrics, baselines).
  • If the paper is available via pdf_url, read it for extraction. Do not extract from abstracts alone for included papers.
Phase 5: Synthesis

Transform extracted records into structured analysis. The synthesis method depends on the output format requested in Phase 1.

Thematic synthesis — Group papers by theme, approach, or finding:

  • Identify recurring themes across papers
  • Note where papers agree, disagree, or address different aspects
  • Highlight methodological trends (what approaches are gaining/losing traction)

Comparative synthesis — Build comparison tables:

MethodPaper(s)DatasetMetricResultLimitations
Method A[1], [3]D1F10.85Domain-specific
Method B[2], [4]D1, D2F10.82Requires X

Chronological synthesis — Map the evolution of the field:

  • What was the state of knowledge at time T?
  • What shifted and why?
  • Where is the field heading?

Gap analysis — Identify what is missing:

  • Questions raised but not answered by existing work
  • Methodological gaps (no one has tried approach X on problem Y)
  • Domain gaps (studied in domain A but not B)
  • Contradictions between studies that remain unresolved
Show full SKILL.md (408 more words)Show less
Phase 6: Output

Produce the review document in the format specified in Phase 1.

Standard structure for a narrative review:

  1. Introduction — Research question, scope, and motivation for the review
  2. Search methodology — Databases searched, queries used, inclusion/exclusion criteria, screening results (N found → N screened → N included)
  3. Findings — Thematic or chronological synthesis of included papers
  4. Discussion — Cross-cutting analysis, trends, contradictions, gaps
  5. Limitations of this review — Search scope restrictions, potential biases, papers not accessible
  6. References — Full citation list for all included papers

Standard structure for a tabular review:

  1. Summary table (all included papers with key metadata)
  2. Comparison matrix (methods × metrics × results)
  3. Gap analysis table (questions × coverage)
  4. Reference list

Citation format: Default to Author et al. (Year) in-text with full references at the end. Adapt to the user's specified format (APA, Chicago, IEEE) if requested.

Quality Checks

Before delivering the review, verify:

  • Every included paper has a structured extraction record
  • Every claim in the synthesis is traceable to at least one extracted finding
  • The gap analysis identifies at least one concrete research opportunity
  • The review acknowledges its own limitations (search scope, access, biases)
  • Citation format is consistent throughout
  • No paper is cited that was excluded during screening
  • Contradictions between papers are noted, not silently resolved by picking a side

Edge Cases

SituationAdaptation
Very few papers found (<5)The field may be nascent. Note this explicitly. Broaden search terms or check if the topic goes by different terminology. Consider adjacent fields.
Too many papers found (>100)Tighten inclusion criteria. Consider limiting to top venues, recent years, or high-citation papers. Produce a scoping review rather than exhaustive review.
User provides a paper list instead of a topicSkip Phase 2 (Search). Start from Phase 3 (Screening) with the provided list.
User wants a related-work section for their own paperTailor synthesis to position the user's contribution. Organize by approaches the user's work builds on, alternatives it competes with, and gaps it fills.
No full-text access to key papersExtract from abstracts and note the limitation. Do not fabricate methodology details. Flag which papers were abstract-only in the extraction records.
Interdisciplinary topicSearch across multiple category prefixes. Note when different fields use different terminology for the same concept.
User asks for a "quick" literature reviewReduce Phase 2 to a single search query, Phase 3 to title-only screening, Phase 4 to abstract-only extraction. Label the output as a preliminary survey, not a systematic review.

© Mathews-Tom, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/literature-review of Mathews-Tom/armory.

  • SKILL.md
  • evals/cases.yaml
  • references/citation-formats.md
  • references/search-strategy.md
  • references/synthesis-framework.md

Open the folder on GitHubat commit 4594fb7

Compare with similar skills

Literature Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Literature Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Literature Review this skillMathews-Tom/armory329—~2.6kAutomated safety check: PassMIT
Literature Reviewneflibata-feng/MyArxiv-Agent12620 repos~5.9kAutomated safety check: NotesMIT
Paper Research on arXivXiaomiMiMo/MiMo-Code14k—~1.5kAutomated safety check: PassMIT
Literature Review AgentAr9av/PaperOrchestra6791 repos~5.2kAutomated safety check: PassCustom licence
Paper AutoratersAr9av/PaperOrchestra6791 repos~1.6kAutomated safety check: PassCustom licence
Daily arXiv Paper Briefjuliye2025/evil-read-arxiv1.7k—~4.3kAutomated safety check: PassNone

Similar skills

  • Literature Review

    neflibata-feng/MyArxiv-Agent

    Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).

    126 GitHub starsUsed in 20 repos~5.9k tokens
    Research & ScienceAuto-check: notes
  • Paper Research on arXiv

    XiaomiMiMo/MiMo-Code

    Searches arXiv, fetches metadata, generates BibTeX, downloads PDFs and finds citations and related papers using a bundled Python script.

    14k GitHub stars~1.5k tokensUpdated 2 days ago
    Research & ScienceAuto-check passed
  • Literature Review Agent

    Ar9av/PaperOrchestra

    Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.

    679 GitHub starsUsed in 1 repo~5.2k tokens
    Research & ScienceAuto-check passed
  • Paper Autoraters

    Ar9av/PaperOrchestra

    Run the four paper-quality autoraters from PaperOrchestra (arXiv:2604.05018, App.

    679 GitHub starsUsed in 1 repo~1.6k tokens
    Research & ScienceAuto-check passed
  • Daily arXiv Paper Brief

    juliye2025/evil-read-arxiv

    Searches arXiv for recent papers matching your research interests, scores them and writes a daily recommendation note into an Obsidian vault.

    1.7k GitHub stars~4.3k tokensUpdated 26 days ago
    Research & ScienceAuto-check passed
  • Paper Orchestra

    Ar9av/PaperOrchestra

    Orchestrate the full PaperOrchestra (Song et al., 2026, arXiv:2604.05018) five-agent pipeline to turn unstructured research materials (idea, experimental log, LaTeX template, conference guidelines…

    679 GitHub starsUsed in 1 repo~3.5k tokens
    Research & ScienceAuto-check passed

More from Mathews-Tom/armory

All 80 skills in this repo
  • Architecture Reviewer

    Mathews-Tom/armory

    Architecture reviews across 7 dimensions (structural, scalability, enterprise readiness, performance, security, ops, data) with scored reports.

    329 GitHub stars~4.6k tokensUpdated 5 days ago
    Auto-check passed
  • Concept To Image

    Mathews-Tom/armory

    Turn concepts into static HTML visuals exported as PNG or SVG files via HTML/CSS/SVG.

    329 GitHub stars~2.6k tokensUpdated 5 days ago
    Auto-check passed
  • Watch

    Mathews-Tom/armory

    A skill your agent uses when analyzing an existing video URL or local recording: "watch this video", "analyze youtube video", "summarize this video", "youtube transcript", "find this moment", "what…

    329 GitHub stars~2.8k tokensUpdated 5 days ago
    Auto-check passed
  • Code Refiner

    Mathews-Tom/armory

    Deep code simplification and refactoring preserving behavior across Python, Go, TypeScript, Rust.

    329 GitHub stars~3.1k tokensUpdated 5 days ago
    Auto-check passed
  • Concept To Video

    Mathews-Tom/armory

    Turn concepts into animated explainer videos using Manim (Python) with MP4/GIF output, audio overlay, multi-scene composition.

    329 GitHub stars~4.9k tokensUpdated 5 days ago
    Auto-check passed
  • Decision Map

    Mathews-Tom/armory

    Maps the unresolved architecture, policy, and scope decisions that must be answered before planning can start: one durable decision ticket per question on the issue tracker, typed and blocker-linked…

    329 GitHub stars~2.7k tokensUpdated 5 days ago
    Auto-check passed

Questions about Literature Review

What does Literature Review do?

Systematic literature review workflow: scope, search (arXiv, Semantic Scholar, Google Scholar), screen, extract, synthesize, and identify gaps. Literature Review is an agent skill from Mathews-Tom/armory. Systematic literature review workflow: scope, search (arXiv, Semantic Scholar, Google Scholar), screen, extract, synthesize, and identify gaps.

When should I use Literature Review?

Literature Review fits situations like: : literature review; survey the literature; systematic review; synthesize the research.

How do I install Literature Review in Claude Code?

Run `npx skills add Mathews-Tom/armory --skill literature-review -a claude-code`. Or copy the skill folder (skills/literature-review in Mathews-Tom/armory) into .claude/skills/literature-review in your project. Claude Code loads it when a task matches its description.

How do I install Literature Review in Codex?

Run `npx skills add Mathews-Tom/armory --skill literature-review -a codex`. Or copy the skill folder (skills/literature-review in Mathews-Tom/armory) into .agents/skills/literature-review in your project. Codex loads it when a task matches its description.

Can I use Literature Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mathews-Tom/armory --skill literature-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/literature-review, .gemini/skills/literature-review, .github/skills/literature-review and .opencode/skills/literature-review in your project.

What does Literature Review need to run?

Going by SKILL.md and its folder, Literature Review needs the command-line tools its instructions call (uv). Our summary lists: Python 3.

Does Literature Review access the network?

SKILL.md names 2 domains. In commands or code: api.semanticscholar.org and connectedpapers.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Literature Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Literature Review use?

Literature Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Literature Review use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.

What are the alternatives to Literature Review?

Skills that share tags, products or a category with Literature Review: Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Paper Research on arXiv (XiaomiMiMo/MiMo-Code, 14k stars), Literature Review Agent (Ar9av/PaperOrchestra, 679 stars) and Paper Autoraters (Ar9av/PaperOrchestra, 679 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Literature Review?

Mathews-Tom (a GitHub user) maintains it in Mathews-Tom/armory, which has 329 GitHub stars. The repository holds 80 skills in this directory. The repository was last updated on October 6, 2026.

Source: Mathews-Tom/armory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.