refs
Skill2 starsChanged 2 months agoMITView on GitHub
Citation neighbourhood of one paper (references and citations from Semantic Scholar, cross-checked with the library) or the citation graph among library papers. Use when the user asks what a paper builds on, who cites it, or what to read first.
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- kaisers-io/refstheir own version, first seen Nov 7, 2026
- dkadts/landing-kit-buildingtheir own version, first seen Aug 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- kaisers-io/refs★ 7same name
- dkadts/landing-kit-building★ 2same 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 20
Add with the download skill (arXiv id or DOI).
≈ “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
refs — citation neighbourhood of a paper, cross-checked with the library
Semantic Scholar references and citations of one paper, split into "already in the library" (reading order by year)
and "not in the library" (ranked by citation count). --library instead maps the citation links between library
papers (the most-cited-within-library papers are the ones to read first).
Arguments: a library key, an arXiv id / link, or a DOI; or library.
python3 zl.py refs <key|arXiv|DOI|link> [--top 15]
python3 zl.py refs --library [--top 20] # ~1 request per library paper, cached in cache/s2/Relay the printed lists; point out which references the user already has and which highly cited ones are missing.
Add with the download skill (arXiv id or DOI). Without S2_API_KEY in .env the API allows about one request per
second; --library on a large library takes a few minutes the first time.
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.

