paper-download
Skill32 starsChanged 32 days agoMITView on GitHub
Use when the user wants full-text PDFs for papers they already identified: one or more DOIs, doi.org links, or a reference list ("下载这几篇论文的 PDF", "把这个 DOI 列表下下来", "download the PDFs for these references"). Tries open access first, then the publisher's TDM API if the user has a key, then (opt-in) the user's own logged-in Chrome. Not for finding papers, Zotero import, or bypassing paywalls.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tsingyuai/scientifytheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tsingyuai/scientify★ 2.2ksame 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.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 45
Add --browser extension only if doctor line 3 is OK and the user agreed to use their Chrome.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
paper-download
Command: auto-paper-download (from https://github.com/jxtse/auto-paper-harvester).
0. Install once
auto-paper-download --help >/dev/null 2>&1 || \
uv tool install git+https://github.com/jxtse/auto-paper-harvester # or: pipx install git+...
auto-paper-download doctordoctor prints three lines, one per download step:
- Open access (OpenAlex / Unpaywall / Crossref). Needs an e-mail address, sent to those
APIs as a contact. If the line starts with
--, ask the user which e-mail to use, then write it to~/.auto-paper-download/.envasOPENALEX_MAILTO=,UNPAYWALL_EMAIL=andCROSSREF_MAILTO=(one per line). Do not invent an address. - Publisher TDM APIs (Elsevier / Wiley / Springer). Optional. Without a key that step is
skipped. Never ask the user to paste keys into the chat; suggest
auto-paper-download ui, which stores them locally. - Browser (the user's own Chrome via the Playwright Extension). Optional and manual:
the user installs the extension, logs in to their library, and pastes the token in
auto-paper-download ui. Only use it ifdoctorshows it ready.
1. Download
auto-paper-download get 10.1016/j.jocs.2020.101171 10.5194/npg-20-705-2013 -o papers --json
auto-paper-download get --file refs.txt -o papers --json # any text with DOIs in it
auto-paper-download get --file refs.txt -o papers --json --browser extension # step 3 on- Tell the user first: how many DOIs, where the files go, whether step 3 is on.
- Add
--browser extensiononly ifdoctorline 3 isOKand the user agreed to use their Chrome. It opens one tab. If a CAPTCHA does not clear by itself the paper is skipped and the site cools down for 24 h. Never solve a CAPTCHA for the user. - Daily caps and per-site pacing are on by default (ledger at
~/.auto-paper-download/ledger.sqlite). Do not pass--no-ledgeror raise limits unless the user asks. Arate_limitedorhost_limitedreason means "try again tomorrow". - Download only papers the user selected. If the list has more than ~50 DOIs, confirm first.
2. Report
--json prints {"requested", "pdfs", "failed": [{"doi", "reason"}], "output_dir"}.
Report: <pdfs>/<requested> saved to <output_dir>, then each failed DOI with its reason in
plain words:
| reason contains | tell the user |
no_source / all sources DownloadError | no open copy found; a TDM key or step 3 may get it |
rate_limited / host_limited / cooldown | daily limit or a site cooling down; retry later |
challenge | the site showed a bot check; it was not solved |
auth_redirect | their browser is not logged in to the library |
Files: <output_dir>/<doi_slug>/<doi_slug>.pdf plus any supplementary PDFs next to it.
Existing files are skipped on re-runs.
More: auto-paper-download get -h, and the repo README.
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.

