fetch-paper
Skill0 starsChanged 4 months agoMITView on GitHub
Downloads an academic paper PDF from open-access sources and saves it to docs/papers/ with the correct slug filename. Accepts an arXiv ID, DOI, or free-form title. Optionally bootstraps a reference doc skeleton.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ShaishavMaisuria/research-paper-lifecycle-skillstheir own version, first seen Nov 1, 2026
- aryankeluskar/skillstheir own version, first seen Jul 7, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ShaishavMaisuria/research-paper-lifecycle-skills★ 59same name
- aryankeluskar/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- analysisSkill
- critiqueSkill
- domain-modelingSkill
- fixesSkill
- grillingSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- literature-reviewSkill
- project-knowledgeSkill
- proposalsSkill
- read-aloudSkill
- referencesSkill
- update-project-knowledgeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 13 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
All network access in this skill is restricted to the following domains.
- Distinctive: line 25
Before querying Unpaywall, always ask the user explicitly:
- Distinctive: line 29
Only proceed if the user explicitly consents and provides or confirms their email for this request.
- Distinctive: line 31
Do not hardcode, infer, persist, or log any email address in this skill or its outputs.
- Distinctive: line 69
If the input was a free-form title and the resolved paper looks wrong (wrong year, different authors), confirm with the user before …
- Distinctive: line 95
If the file already exists, report it and stop:
- Distinctive: line 113
Verify the file is a valid PDF (not an HTML error page):
- Very specific: line 118
If file reports HTML or ASCII text, delete the file and proceed to the next tier.
- Very specific: line 128
Verify with file as above.
- Distinctive: line 132
Ask the user for consent per the Personal information policy above.
- Very specific: line 144
Verify with file as above.
- Distinctive: line 154
If all automated tiers fail, ask:
- Distinctive: line 167
After a successful download or file copy:
- Very specific: line 169
Check if docs/references/{slug}.md exists:
- Distinctive: line 174
If it exists: note the path and skip.
- Distinctive: line 176
If it does not exist: ask the user:
- Very specific: line 179
If yes: copy the template from .claude/skills/references/templates/reference.md, fill in the following fields from the resolved metadata, …
- Very specific: line 186
Do not fill in Abstract, Summary, Introduction, Method, Results, Discussion, or Conclusion — leave all as {Not available — paper not read}.
- Distinctive: line 211
Never retry in a loop. If a source fails once, move to the next tier.
- Very specific: line 219
Ambiguous title slug: use the most recognisable abbreviation (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Safe URLs
All network access in this skill is restricted to the following domains. Never fetch from any domain not on this list without explicit user confirmation.
| Domain | Purpose |
export.arxiv.org | Metadata resolution via Atom XML |
arxiv.org | PDF download |
api.semanticscholar.org | Paper search, OA PDF URL, author/year metadata |
api.openalex.org | OA URL fallback via DOI |
api.unpaywall.org | OA PDF URL fallback via DOI (requires consent — see below) |
ar5iv.org | HTML paper render (last automated resort, not a PDF) |
Personal information policy
Unpaywall requires an email address as a courtesy identifier in the query string (?email=...). This is the only API in the fallback chain that uses personal information.
Before querying Unpaywall, always ask the user explicitly:
"Unpaywall requires an email address as a usage identifier. May I include your email in this request? (It will be sent as a plain URL parameter to api.unpaywall.org — not stored by this skill.)"
Only proceed if the user explicitly consents and provides or confirms their email for this request. If the user declines, skip Unpaywall and move to the next fallback tier.
Do not hardcode, infer, persist, or log any email address in this skill or its outputs.
Trigger
This skill is invoked explicitly: /fetch-paper {input} where {input} is one of:
- arXiv ID — e.g.
1703.03864orarXiv:1703.03864 - DOI — e.g.
10.1162/106365602320169811 - Free-form title — e.g.
"Evolving Neural Networks through Augmenting Topologies" - Direct PDF URL — e.g.
https://arxiv.org/pdf/1703.03864
It may also fire automatically when the references skill creates a new reference doc but no corresponding PDF exists in docs/papers/.
Phase 0 — Resolution (Explore agent)
Spawn an Explore subagent (not general-purpose) with this exact brief, substituting {input}. The agent must only access domains listed in the Safe URLs table above.
Given this input —
{input}(arXiv ID / DOI / title / URL) — resolve it to a canonical paper record. Query in this order:
- If the input contains an arXiv ID: fetch
https://export.arxiv.org/abs/{arxiv_id}for metadata. The PDF URL ishttps://arxiv.org/pdf/{arxiv_id}.- Query Semantic Scholar:
https://api.semanticscholar.org/graph/v1/paper/search?query={title_or_id}&fields=title,externalIds,year,authors,openAccessPdf— extractexternalIds.ArXiv,externalIds.DOI,year,authors[].name,openAccessPdf.url.- If a DOI is known, query OpenAlex:
https://api.openalex.org/works/doi:{doi}— extractopen_access.oa_url,title,publication_year,authorships[].author.display_name.- Do not query Unpaywall — it requires personal information consent that must be handled in the main conversation, not delegated to an agent.
Return ONLY a compact record with these fields (omit any that are unavailable):
arxiv_id: string or nulldoi: string or nullauthors: list of last names only (lowercase)year: 4-digit integertitle: full title stringoa_pdf_url: direct PDF URL or null
The agent returns one compact record. Do not let it return raw JSON blobs or API response bodies.
If the input was a free-form title and the resolved paper looks wrong (wrong year, different authors), confirm with the user before proceeding.
Phase 1 — Slug construction and duplicate check
From the resolved record, derive the slug using the project's filename convention:
{authors}-{year}-{short-title}authors: all co-authors' last names, hyphen-separated, lowercase (e.g.stanley-miikkulainen,salimans-ho-chen-sidor-sutskever)year: 4-digit publication yearshort-title: 3–5 word kebab-case slug of the paper title — use editorial judgment, not mechanical truncation
Examples from this project:
salimans-2017-es-scalable-alternative-rlstanley-miikkulainen-2002-neatstanley-damprosio-gauci-2009-hyperneat
Check for existing file:
ls docs/papers/{slug}.pdf 2>/dev/nullIf the file already exists, report it and stop:
Already saved → docs/papers/{slug}.pdfPhase 2 — PDF download (native, fallback chain)
Attempt sources in priority order, stopping at the first success. All downloads use native Bash with curl. Only access domains in the Safe URLs table.
Tier 1 — arXiv direct (if arxiv_id is known)
curl -L --max-time 60 -o docs/papers/{slug}.pdf \
"https://arxiv.org/pdf/{arxiv_id}"Verify the file is a valid PDF (not an HTML error page):
file docs/papers/{slug}.pdfIf file reports HTML or ASCII text, delete the file and proceed to the next tier.
Apply a 3-second delay before downloading a second arXiv PDF in the same session to respect rate limits.
Tier 2 — OA URL from agent (if oa_pdf_url was returned)
curl -L --max-time 60 -o docs/papers/{slug}.pdf "{oa_pdf_url}"Verify with file as above. If the OA URL resolves to a domain not in the Safe URLs table, ask the user for confirmation before proceeding.
Tier 3 — Unpaywall (DOI required, consent required)
Ask the user for consent per the Personal information policy above. If consent is given and an email is provided:
curl -s "https://api.unpaywall.org/v2/{doi}?email={user_email}"Extract best_oa_location.url_for_pdf from the JSON response, then download:
curl -L --max-time 60 -o docs/papers/{slug}.pdf "{oa_pdf_url}"Verify with file as above.
Tier 4 — ar5iv HTML (arXiv papers only, last automated resort)
https://ar5iv.org/abs/{arxiv_id} renders the paper as HTML — it is not a PDF. Only use this tier if the user only needs to read the paper and does not need a file in docs/papers/. Note the limitation explicitly:
"Could not download a PDF. Retrieved HTML render at ar5iv.org — the paper is readable but no file has been saved to docs/papers/."
Tier 5 — User fallback
If all automated tiers fail, ask:
"No open-access PDF was found for this paper. If you have a local copy, provide the path (e.g.
/home/user/Downloads/paper.pdf) and I will copy it todocs/papers/{slug}.pdf."
On user reply with a path:
cp "{user_path}" docs/papers/{slug}.pdfPhase 3 — Reference doc bootstrap (optional)
After a successful download or file copy:
- Check if
docs/references/{slug}.mdexists:ls docs/references/{slug}.md 2>/dev/null - If it exists: note the path and skip.
If it does not exist: ask the user:
"Create a reference doc skeleton at
docs/references/{slug}.md?"If yes: copy the template from
.claude/skills/references/templates/reference.md, fill in the following fields from the resolved metadata, and set all content sections to{Not available — paper not read}:# {Title}— full paper title**Authors:**— full names (not just last names)**Year:****Venue:**— journal/conference if known, otherwisearXiv:{arxiv_id}or{Not available}**DOI / URL:**— DOI URL or arXiv abstract URL
Do not fill in Abstract, Summary, Introduction, Method, Results, Discussion, or Conclusion — leave all as
{Not available — paper not read}. Those sections are filled separately after reading the paper.
Phase 4 — Report
Print a compact summary:
Saved → docs/papers/{slug}.pdf ({file size})
Ref → docs/references/{slug}.md [created | already exists | skipped]
Source → {tier that succeeded: arXiv | OA URL ({source}) | Unpaywall | user-provided}Rate limits and constraints
| Source | Limit | Handling |
| arXiv PDF | ~1 request/3s recommended | Add sleep 3 between consecutive downloads |
| Semantic Scholar | 1 req/sec unauthenticated (shared pool) | Single call only; no retry loop |
| OpenAlex | Fair use, no stated limit for single lookups | Single call only |
| Unpaywall | Free API, single lookup | Requires explicit user consent before each use |
Never retry in a loop. If a source fails once, move to the next tier.
Slug edge cases
- Single author: just the last name —
syswerda-1991-steady-state-ga - Many authors: include all last names —
salimans-ho-chen-sidor-sutskever-2017-es-scalable-alternative-rl. If this becomes unwieldy (5+ authors), use first-author +etal—salimans-etal-2017-es-scalable-alternative-rl— but prefer full listing when practical. - Ambiguous title slug: use the most recognisable abbreviation (e.g.
neatfor NeuroEvolution of Augmenting Topologies) rather than mechanically truncating the title.
Interaction with the references skill
The references skill governs when reference docs are created and how they must be written. This skill governs how PDFs are obtained. They are complementary — neither calls the other automatically. A natural follow-up after /fetch-paper is to read the downloaded PDF and fill in the docs/references/{slug}.md sections.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

