Search scientific literature (OpenAlex, Semantic Scholar, arXiv, PubMed, TechRxiv, Research Square, IACR ePrint; Europe PMC and Crossref on request), walk citations, find open-access copies, export BibTeX, or run a local-LLM novelty assessment. Use whenever the user asks to find papers, check prior art or the state of the art, assess novelty of a claim, list what cites a paper, get a reading list, or says "litsurvey". Prefer this over generic web search for scholarly questions.
Scanned 9/19/2026
npx -y skills add udaykdk/litsurvey --skill litsurvey --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Litsurvey?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/udaykdk-litsurvey)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: litsurvey
description: Search scientific literature (OpenAlex, Semantic Scholar, arXiv, PubMed, TechRxiv, Research Square, IACR ePrint; Europe PMC and Crossref on request), walk citations, find open-access copies, export BibTeX, or run a local-LLM novelty assessment. Use whenever the user asks to find papers, check prior art or the state of the art, assess novelty of a claim, list what cites a paper, get a reading list, or says "litsurvey". Prefer this over generic web search for scholarly questions.
---
# litsurvey: scholarly search and novelty assessment
`litsurvey` is a command on PATH (if not, try `python3 -m litsurvey`).
Configuration lives in `~/.litsurvey/config.json`; never ask the user for
API keys and never print that file.
## Commands
```bash
litsurvey search "keyword query" -n 15 [--year-from 2022] [--sort citations|year] [--abstracts] [--json] [--out refs.bib]
# [--sources openalex,s2,arxiv] to go faster, [--sources ...,europepmc,crossref] to go wider
litsurvey paper <id|title> # id: S2 hash, DOI:10..., or ARXIV:2404.19756; a title gives a numbered candidate list (exit 2): rerun with --pick N
litsurvey cites <id> [-n 20] # forward snowball: who cites it
litsurvey refs <id> [-n 20] # backward snowball: what it cites
litsurvey related <id> [-n 20] # similar papers via recommender (different vocabulary)
litsurvey oa <doi> # legal open-access PDF via Unpaywall
litsurvey novelty "claim as generic topic" [--rounds 8] [--out report.md] # local-LLM agent, minutes
litsurvey research "question" [--rounds 12] [--out survey.md] # local-LLM agent, minutes
litsurvey history [show <id> | export <id> --out x.bib | delete <id>]
litsurvey doctor # run this first if anything fails
```
## How to use it well
- For a literature question, run 2 to 4 `search` calls with different
phrasings (synonyms, method-centric and application-centric), then
`cites`/`related` on the closest hits. Use `--json` when you will process
results further.
- Cite only titles, DOIs and URLs that appear in the tool output. Do not
reformat references from memory.
- `novelty` and `research` hand the whole job to the user's local model and
take minutes; run them in the background. Use them when the user asks for
the local agent or is working on confidential material; otherwise drive
`search`/`cites`/`related` yourself and synthesise.
- To read a paper: `oa <doi>` for a PDF link, or fetch
`https://arxiv.org/html/<arxiv id>` for arXiv full text.
- Semantic Scholar is limited to 1 request/second; do not run litsurvey
commands in parallel.
## Confidentiality rule
Users may be reviewing confidential manuscripts. Queries must be short
generic keyword phrases. Never put verbatim sentences, titles, author names
or identifying phrasing from a manuscript into a query, and never send
manuscript text to any web service.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!