alphaxiv
Skill9 starsChanged 5 months agoMITView on GitHub
Ingest a paper from AlphaXiv/arXiv (by arXiv ID or title) into a structured source file — fetches metadata, abstract, and the AI overview via the AlphaXiv API
5 other projects use a version of this.
Adopted by
Most recently taken up by
- talhaMah56/claude_skillstheir own version, first seen Sep 12, 2026
- wanshuiyin/Auto-claude-code-research-in-sleeptheir own version, first seen Jul 15, 2026
- Immortalqx/my_codex_skillstheir own version, first seen Jun 10, 2026
- Chanw-research/claude-code-paper-writingtheir own version, first seen May 10, 2026
- raja21068/AutoResearchtheir own version, first seen May 5, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- wanshuiyin/Auto-claude-code-research-in-sleep★ 19ksame name
- Immortalqx/my_codex_skills★ 54same name
- Chanw-research/claude-code-paper-writing★ 42same name
- raja21068/AutoResearch★ 2same name
- talhaMah56/claude_skills★ 0same 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.
- .claude/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- askSkill
- autoexploreSkill
- collateSkill
- curriculumSkill
- editSkill
- goalSkill
- notionSkill
- obsidianSkill
- retrieveSkill
- tutorSkill
- webSkill
- zoteroSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
If $ARGUMENTS is empty, ask the user for an arXiv ID or paper title, then continue.
- Very specific: line 29
If $ARGUMENTS is an arXiv ID (e.g.
- Very specific: line 43
Format: Write the file following .claude/Templates/source.md for the frontmatter contract, with exactly this structure (no need to consult …
- Distinctive: line 83
Propose: After writing, ask the user:
- Very specific: line 84
Run /collate <title> to synthesise this source into a paper page?
- Very specific: line 85
Run /collate <topic> for any new concepts introduced?
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ingest a paper from AlphaXiv (an arXiv front-end with
AI overviews and metadata) into sources/alphaxiv_<slug>.md. Unlike /zotero,
there's no local PDF — content is fetched from the AlphaXiv API: bibliographic
metadata, the abstract, and an AI-generated overview. This is normally invoked by
/collate as an ingestion step, but can be run directly.
If $ARGUMENTS is empty, ask the user for an arXiv ID or paper title, then continue.
Layout
Output goes to the personal sources/ by default. When invoked by /curriculum,
write instead to that course's per-course library course/<slug>/library/ (the
caller passes the destination directory) — fetched course material stays out of the
personal base until the learner masters it and /tutor promotes it. Either way the
filename is alphaxiv_<slug>.md.
Template: .claude/Templates/source.md. The fetch tool is
.claude/skills/alphaxiv/scripts/alphaxiv.py (stdlib only; the ingestion commands
below need no API key).
Steps
- Resolve the paper.
- If $ARGUMENTS is an arXiv ID (e.g.
2006.11239or2006.11239v2), use it. - Otherwise treat it as a title/topic and search, then confirm the match with the
user before ingesting:
sh .claude/src/pyrun --need any .claude/skills/alphaxiv/scripts/alphaxiv.py search "$ARGUMENTS" --limit 5
- If $ARGUMENTS is an arXiv ID (e.g.
- Extract. Fetch the objective content for the resolved arXiv ID
<id>:sh .claude/src/pyrun --need any .claude/skills/alphaxiv/scripts/alphaxiv.py paper <id> # title, authors, date, abstract sh .claude/src/pyrun --need any .claude/skills/alphaxiv/scripts/alphaxiv.py metadata <id> # authors, institutions, topics, GitHub sh .claude/src/pyrun --need any .claude/skills/alphaxiv/scripts/alphaxiv.py overview <id> # AI-generated overview Format. Write the file following
.claude/Templates/source.mdfor the frontmatter contract, with exactly this structure (no need to consult other source files):--- type: alphaxiv_source title: <paper title> concepts_mentioned: [<AlphaXiv topics + key concepts from the abstract>] source_links: - https://arxiv.org/abs/<id> - https://www.alphaxiv.org/abs/<id> --- ## Content ### Abstract <the paper abstract, verbatim> ### AI overview (AlphaXiv — AI-generated) <the AlphaXiv AI overview; this is AI-generated, not the authors' own text> ### Metadata - Authors: <...> - Institutions: <...> - Published: <date> - Topics: <...> - Code: <GitHub URL, if any>source_linksholds URLs (a remote source has no local file). This is metadata + abstract + AI overview — not the full paper text; for full text, ingest the PDF via/zotero.- Write. Slugify the title to snake_case and write
<dest>/alphaxiv_<slug>.md, where<dest>issources/by default orcourse/<slug>/library/when/curriculuminvoked this skill. If it exists, ask before overwriting. - Propose. After writing, ask the user:
- Run
/collate <title>to synthesise this source into a paper page? - Run
/collate <topic>for any new concepts introduced?
- Run
Notes
- Vendored, security-reviewed script from
danjuan-77/alphaxiv-skill (MIT, see
LICENSEin this folder). It calls onlyhttps://api.alphaxiv.org. - The ingestion commands (
search,paper,metadata,overview) need no token. The script also has anaskcommand that needsALPHAXIV_TOKEN; it's not used by this skill.
Wrap up
Report: the file written, concepts extracted, anything skipped (one-line reason each).
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.

