paper-fetchlisted

Retrieve one specified academic paper (by title, arXiv ID, DOI, URL, or a local .md/.txt/.pdf path the caller already has) and land it on disk as source.md plus a source.meta.json carrying a line-number section index. Checks context/papers/ for an existing copy first; local files and direct PDF URLs are read directly with no search at all, while other references use alphaxiv, Semantic Scholar routing, then bioRxiv/medRxiv. Use this as the mandatory first step whenever any other paper-reading SOP in this package needs the actual text of a paper — it is the sole entry point of the pipeline and every downstream SOP reads the files it lands, so do not bypass it even when the caller already has the file. If it returns not_found, halt immediately; do not fabricate content or guess at the paper's likely contents.
yogsoth-ai/paper-reading · ★ 1 · Data & Documents · score 80

Install: claude install-skill yogsoth-ai/paper-reading

# Paper Fetch If the caller already has the paper — a local `.md`/`.txt`/`.pdf` path, or a direct HTTP(S) PDF URL (path ends in `.pdf`, ignoring query and fragment) — read it directly before considering any search route. Record `source_channel` as `local_file`, `local_pdf`, or `direct_pdf`. If the read fails, return `not_found` and do not fall back to alphaxiv, Semantic Scholar, bioRxiv, or medRxiv. The pipeline's sole entry point: retrieves a paper and lands it on disk. It checks the cache first, reads already-identified sources (local files, direct PDF URLs) with no search at all, and otherwise uses the fixed fallback (alphaxiv → Semantic Scholar routing → bioRxiv/medRxiv → not_found). Decoupled from `literature-engine`'s `literature-research`/`literature-search`/ `literature-overview` — this SOP holds its own retrieval calls rather than delegating. ## Why an already-supplied file still enters through this SOP Skipping straight to a reading SOP with the caller's own path looks like it saves a step, but 13 downstream SOPs take `meta_path` and read only section line ranges (`star-awarding` reads method + results; `first-pass-skim`'s "headings only, never bodies" constraint holds *because* it is handed shallow ranges). A bare path carries no index, and a bare `.pdf` carries no extracted text at all. So the thing to skip is the **four-channel search**, not the landing and indexing. That is what Step 1 does: no network lookup, same landing step, same output contract. Tactic