Agent Native

literature-review

This skill searches arXiv for relevant papers on a given research topic, downloads their source files, and synthesizes findings into a structured literature…

by ImbueOfficial publisherNot reviewed

Identity proven by GitHub's verified organisation badge (imbue-ai)

Agents
Claude Code
License
AGPL-3.0 (copyleft)
Pin
a2ee48cpinned Oct 9, 2026
Context cost
about 1,400 tokenswhen the skill loads
GitHub stars
36on imbue-ai/catalyst
Scripts
None found

What it does

“Search arXiv for relevant papers, download papers, and produce a structured literature review”
The author's description, from SKILL.md

Generated summary from the skill's own text

This skill searches arXiv for relevant papers on a given research topic, downloads their source files, and synthesizes findings into a structured literature review document. The agent performs multiple targeted searches, validates paper relevance through abstracts, extracts key contributions and methods, and organizes results into themes, agreements, disagreements, and open questions.

When to use it

  • Surveying current research on a new or unfamiliar topic
  • Gathering foundational papers before writing theory or proposing methods
  • Understanding what approaches exist and where gaps remain in a field
  • Building grounded context before starting a research project

When not to

  • Finding papers outside academic arXiv repositories
  • Needing access to proprietary or paywalled research only
  • When quick answers suffice and full paper analysis is unnecessary

Install

These commands install from the publisher's repository and need no account.

skills CLI

npx skills add imbue-ai/catalyst --skill literature-review

Installs from the repository's default branch, which may have changed since the commit we checked.

GitHub CLI 2.90 or later

gh skill install imbue-ai/catalyst literature-review@a2ee48c34741df5d4549d97b22aa44589d9eaa6a

Installs the commit we checked (a2ee48c).

Copy by hand

Download the folder at a2ee48c and put it in .claude/skills/literature-review for Claude Code and in .agents/skills/literature-review for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode.

Skill folder on GitHub at a2ee48c

Copy for your agent

A prompt for any coding agent. It installs this skill from GitHub at the pinned commit, copies the files as they are, and runs nothing unless you ask.

Prompt

Install the agent skill "literature-review" by Imbue.

Source, pinned to commit a2ee48c34741df5d4549d97b22aa44589d9eaa6a:
https://github.com/imbue-ai/catalyst/tree/a2ee48c34741df5d4549d97b22aa44589d9eaa6a/src/claude_skills/skills/literature-review

1. Download that folder at exactly this commit. Do not use the default branch.
2. Copy every file unchanged, keeping the folder structure, into .claude/skills/literature-review/ for Claude Code and .agents/skills/literature-review/ for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode. Create the folders if they do not exist.
3. Do not edit the files, and do not run any script in the folder unless I ask you to.
4. When you are done, list the files you copied and where you put them.

Listing and checks: https://www.agentnative.dev/skills/imbue/literature-review

SKILL.md at the pin

---
name: literature-review
description: "Search arXiv for relevant papers, download papers, and produce a structured literature review"
argument-hint: "topic or research question to survey (e.g. 'bifurcation in shallow ReLU networks')"
---

You are a **Scientific Literature Reviewer**. Your goal is to find, download, and synthesize relevant research papers from arXiv (and other sources) on a given topic.

## Mandate
- Cast a wide net: find **at least 8-12 relevant papers**, more if the topic is broad.
- Prioritize relevance and recency, but include foundational/seminal work when appropriate.
- Relevant literature can include work that falsifies or bounds the topic, not just work that supports it.
- Download the full papers (TeX source or PDF) so downstream agents can reference the original papers.
- Read each paper and extract key findings, methods, and results. However, skip appendix sections and/or supplementary material to avoid exhausting context size limits.
- Produce a structured summary that a theory-writing agent can use as grounding.

## Input
Arguments: $ARGUMENTS

## Folder setup
All commands must be run in the current working directory. Do not `cd` anywhere else, do not try to use the global `/tmp` folder or TMPDIR (only use the local `./tmp` folder).

Create a separate output folder for your artifacts:
OUTPUT_DIR: `mktemp -d -p ./tmp literature-review-XXXX`

Then create a subfolder for storing downloaded papers:
```bash
mkdir "<OUTPUT_DIR>/papers"
```

- `<OUTPUT_DIR>/papers/` — downloaded papers (TeX source or PDF) go here
- `<OUTPUT_DIR>/summary.md` — your final structured summary (required filename)

If you need to store any additional intermediate files (e.g. one-off Python scripts), do so under `<OUTPUT_DIR>/`. Do not write outside of this folder.

## Search Strategy
Use multiple search queries to maximize coverage:

1. **Direct query**: Search for the exact topic.
2. **Broader terms**: Search for parent concepts or related fields.
3. **Specific techniques**: Search for key methods or algorithms mentioned in the topic.
4. **Author follow-up**: If you find a highly relevant paper, search for other work by the same authors.

For each search, use `WebSearch` to find papers. Target arXiv specifically (include "arxiv" or "site:arxiv.org" in queries). Also consider Google Scholar queries.

## Summary File Format
Your `summary.md` file must follow this structure:

```
# Literature Review: [Topic]

## Overview
[2-3 paragraph summary of the research landscape: what's known, what's debated, what's open]

## Papers

### [Paper Title] (arXiv:XXXX.XXXXX)
- **Authors**: [author list]
- **Year**: [year]
- **Full paper**: papers/XXXX.XXXXX.pdf or papers/XXXX.XXXXX/XXX.tex
- **Core contribution**: [1-2 sentences]
- **Key findings**:
  - [finding 1]
  - [finding 2]
- **Methods**: [brief description of approach]
- **Relevance to topic**: [why this paper matters for the research question]

### [Next Paper Title] ...
...

## Synthesis
### Key Themes
[What patterns emerge across the literature?]

### Agreements and Disagreements
[Where do papers converge? Where do they conflict?]

### Gaps and Open Questions
[What hasn't been addressed? What would a new theory need to explain?]

### Methodological Notes
[Common experimental setups, benchmarks, or proof techniques used across papers]
```

## Execution Steps
1. **Search**: Run at least 4-5 different search queries using `WebSearch` to find relevant arXiv papers. For each query, examine the results and identify papers that are genuinely relevant to the topic.
2. **Validate relevance**: For each candidate paper, fetch its arXiv abstract page using `WebFetch` to read the full abstract. Discard papers that are only superficially related. Keep papers that directly address the phenomenon, use relevant methods, or provide theoretical foundations.
3. **Download TeX source or PDF**: For each relevant paper, try to download the TeX source and extract it:
   ```bash
   curl -L -OJ --no-progress-meter -w "%{filename_effective}\n" --output-dir "<OUTPUT_DIR>/papers" "https://arxiv.org/src/XXXX.XXXXX"
   # If .tar.gz was downloaded:
   mkdir "<OUTPUT_DIR>/papers/XXXX.XXXXX"
   tar -xzvf "<OUTPUT_DIR>/papers/<DOWNLOADED FILENAME>" -C "<OUTPUT_DIR>/papers/XXXX.XXXXX"
   rm "<OUTPUT_DIR>/papers/<DOWNLOADED FILENAME>"
   # For other file endings (e.g. .gz), use the appropriate tool to extract it to "<OUTPUT_DIR>/papers/XXXX.XXXXX/"
   ```
   Look for the main `.tex` filename in the tar output to reference it in your summary.
   ONLY IF the TeX source is not available for a particular paper, download the PDF instead:
   ```bash
   curl -L --no-progress-meter "https://arxiv.org/pdf/XXXX.XXXXX.pdf" -o "<OUTPUT_DIR>/papers/XXXX.XXXXX.pdf"
   ```
   ALWAYS TRY to obtain a TeX source first for each paper. TeX is easier for downstream agents to process than PDF files.
4. **Read and extract**: Read each downloaded paper. Make sure you skip any appendix sections and/or supplementary material to avoid exhausting context size limits. For each paper, extract:
   - Title and authors
   - Core contribution / main findings
   - Key methods and techniques
   - Results relevant to the topic
   - Limitations noted by the authors
5. **Synthesize**: Write the file `<OUTPUT_DIR>/summary.md`, according to the summary file format specified above.
6. **Store results**: Persist your output and return the literature review ID:
   ```bash
   uv run python <SKILL_BASE_DIR>/scripts/context_manager.py store_results --from_agent_type literature-review --from_folder <OUTPUT_DIR>
   ```
   Note down the returned literature ID (e.g. `L_20260414_143052_a1b2c3`) as the result of this skill.

From imbue-ai/catalyst at a2ee48c, shown as plain text under its license: AGPL-3.0 (copyleft). The license text is in LICENSE.

View SKILL.md on GitHub at a2ee48c

Files

1 file, 5.7 KB in total. Each file has a sha256 in the pin's manifest; the first 12 characters are shown.

Skill folder on GitHub at a2ee48c
All 50 skills from Imbue

More from Imbue

  • architect

    Generates an architecture document for a feature by reading the existing spec, analyzing the codebase deeply, and conducting guided Q&A with the user to…

    Claude Code · about 4K tokens · pinned 6 days ago

  • build

    This skill executes a multi-step implementation plan by working through task files sequentially.

    Claude Code · about 1.1K tokens · pinned 6 days ago

  • build-sculptor-extension

    Build or modify Sculptor extensions, which are runtime ES modules that add panels, overlays, widgets, home views, or settings UI to the Sculptor frontend.

    Contains scripts

    Claude Code, Codex, Cursor +3 · about 3.3K tokens · pinned 6 days ago

  • fix-bug

    Fixes bugs using test-driven development with an interactive or autonomous workflow.

    Claude Code · about 9.8K tokens · pinned 6 days ago

  • handoff

    This skill hands off ongoing work to a fresh agent, either in the same workspace or a new isolated workspace, while preserving context through a synthesized…

    Claude Code · about 1.1K tokens · pinned 6 days ago

  • help

    This skill fetches the latest Sculptor documentation from GitHub and answers user questions about how to use Sculptor's features, including workspaces…

    Claude Code · about 880 tokens · pinned 6 days ago

All Docs and writing skills
  • n8n-docs-assistant

    This skill answers questions about n8n configuration, setup, credentials, nodes, and troubleshooting by retrieving information from current n8n documentation.

    by n8nOfficial publisher

    Claude Code, Codex, Cursor +3 · about 450 tokens · pinned 6 days ago

  • algodocs-automation

    This skill automates Algodocs document processing tasks through Composio's toolkit via the Rube MCP server.

    by ComposioOfficial publisher

    Claude Code, Codex, Cursor +3 · about 690 tokens · pinned 6 days ago

  • remotion-docs

    This skill enables agents to search and retrieve Remotion documentation via the Algolia API and fetch pages as Markdown.

    by RemotionOfficial publisher

    Claude Code, Codex, Cursor +3 · about 320 tokens · pinned 6 days ago

  • remotion-docs

    This skill searches the Remotion documentation using the Algolia API and retrieves documentation pages as Markdown.

    by RemotionOfficial publisher

    Claude Code, Codex, Cursor +3 · about 320 tokens · pinned 6 days ago

  • receipts

    This skill generates a personal Claude Code usage report from local session transcripts stored in ~/.claude/projects, mining activity across projects without…

    by AnthropicOfficial publisher

    Contains scripts

    Claude Code · about 4.1K tokens · pinned 6 days ago

  • solo

    This skill enables an agent to work through a single difficult mathematics problem independently within one session.

    by AnthropicOfficial publisher

    Claude Code · about 1.4K tokens · pinned 6 days ago

The skills listed here are third-party software, collected from public GitHub repositories as a catalog of recent skills and provided as is. Agent Native does not write or control them and is not responsible for any harm, loss or damage caused by installing or using them. Labels and checks describe what we saw at one commit and are not a guarantee. Read a skill's files before you run it. Terms of use