alphaxiv
Skill2 starsChanged 6 months agoMITView on GitHub
Quick single-paper lookup via AlphaXiv LLM-optimized summaries with tiered source fallback. Use when user says "explain this paper", "summarize paper", pastes an arXiv/AlphaXiv URL, or provides a bare arXiv ID for quick understanding - not for broad literature search.
We split this skill into the rules it gives an agent
9 rules. 5 are common, 1 is distinctive, and 3 are very specific to this project.
5
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 62
If the overview answers the user's question, stop here.
- Distinctive: line 64
If the request fails (HTTP 404 — paper not yet processed) or the content is insufficient, proceed to Step 3.
- Common: line 75
If this still does not answer the question, proceed to Step 4.
- Very specific: line 79
When the overview and full markdown are both insufficient (e.g., the user asks about equations, proofs, appendix details, or implementation …
- Common: line 89
Do NOT read the entire source tree by default: Read selectively.
- Common: line 115
If the user only asks for one specific detail, answer it directly — skip the full template.
- Very specific: line 154
If wiki was not present at read time (or the helper was unreachable), the user can backfill via python3 "$WIKI_SCRIPT" sync research-wiki/ …
- Common: line 163
Cross-platform: When downloading and extracting the source archive, prefer cross-platform approaches (e.g., Python stdlib) over …
- Very specific: line 184
After /research-lit, /novelty-check, or /idea-discovery surface a specific paper, users can invoke /alphaxiv PAPER_ID for a fast deep-dive …
“Common” is measured: kept by at least 6 in 10 of the 4 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
AlphaXiv Paper Lookup
Lookup paper: $ARGUMENTS
Quick single-paper reader with tiered source fallback (overview → full markdown → LaTeX source). Powered by AlphaXiv.
Role & Positioning
This skill is the quick single-paper reader that returns LLM-optimized summaries:
| Skill | Source | Best for |
/arxiv | arXiv API | Batch search, PDF download, metadata |
/deepxiv | DeepXiv SDK | Progressive section-level reading |
/semantic-scholar | S2 API | Published venue metadata, citation counts |
/alphaxiv | alphaxiv.org | Instant LLM-optimized summary of one paper, with LaTeX source fallback |
Do NOT use this skill for topic discovery, broad literature search, or multi-paper surveys — use /research-lit or /arxiv instead.
Constants
- OVERVIEW_URL =
https://alphaxiv.org/overview/{PAPER_ID}.md - ABS_URL =
https://alphaxiv.org/abs/{PAPER_ID}.md - ARXIV_SRC_URL =
https://arxiv.org/src/{PAPER_ID}
Overrides (append to arguments):
/alphaxiv 2401.12345— quick overview/alphaxiv "https://arxiv.org/abs/2401.12345"— auto-extract ID/alphaxiv 2401.12345 - depth: src— force LaTeX source inspection/alphaxiv 2401.12345 - depth: abs— force full markdown
Workflow
Step 1: Parse Arguments & Extract Paper ID
Parse $ARGUMENTS to extract a bare arXiv paper ID. Accept these input formats:
https://arxiv.org/abs/2401.12345orhttps://arxiv.org/abs/2401.12345v2https://arxiv.org/pdf/2401.12345https://alphaxiv.org/overview/2401.12345https://alphaxiv.org/abs/2401.123452401.12345or2401.12345v2
Strip version suffixes (v1, v2, ...) for API calls. Store as PAPER_ID.
Parse optional directives:
- depth: overview|abs|src: force a specific tier instead of cascading
Step 2: Fetch AlphaXiv Overview (Tier 1 — Fastest)
Fetch the structured overview from https://alphaxiv.org/overview/{PAPER_ID}.md.
This returns a structured, LLM-optimized report designed for machine consumption. Use this as the default and preferred source.
If the overview answers the user's question, stop here. Do not fetch deeper tiers unnecessarily.
If the request fails (HTTP 404 — paper not yet processed) or the content is insufficient, proceed to Step 3.
Step 3: Fetch Full AlphaXiv Markdown (Tier 2 — More Detail)
Fetch the full paper markdown from https://alphaxiv.org/abs/{PAPER_ID}.md.
This provides the full paper body as markdown. Use when the user needs:
- Specific methodology details
- Detailed experimental results
- Particular sections not covered in the overview
If this still does not answer the question, proceed to Step 4.
Step 4: Fetch arXiv LaTeX Source (Tier 3 — Deepest)
When the overview and full markdown are both insufficient (e.g., the user asks about equations, proofs, appendix details, or implementation specifics), download the paper's LaTeX source from https://arxiv.org/src/{PAPER_ID}.
The source is a .tar.gz archive. Download it to a temporary directory, extract it, and list the .tex files inside.
Then inspect only the files needed to answer the question. Prioritize:
- Top-level
*.texfiles (usually the main document) - Files referenced by
\input{}or\include{} - Appendices, tables, or sections directly related to the user's question
Do NOT read the entire source tree by default. Read selectively.
Temporary source artifacts live under /tmp. Do not rely on persistence.
Step 5: Present Results
Default Answer Shape
## [Paper Title]
- **arXiv**: [PAPER_ID] — https://arxiv.org/abs/[PAPER_ID]
- **Source depth**: overview | abs | src
### Summary
[2-3 sentence summary]
### Key Points
- [point 1]
- [point 2]
- [point 3]
### Answer to Your Question
[Direct answer if the user asked a specific question]If the user only asks for one specific detail, answer it directly — skip the full template.
Suggest Follow-Up Skills
/arxiv "PAPER_ID" - download - download the PDF to local library
/deepxiv "PAPER_ID" - section: Methods - read a specific section progressively
/research-lit "related topic" - multi-source literature survey
/novelty-check "idea from paper" - verify novelty against this paper's areaUpdate Research Wiki (if active)
Required when research-wiki/ exists in the project; skip silently
otherwise. When the wiki dir exists, resolve $WIKI_SCRIPT per the
canonical chain at
shared-references/wiki-helper-resolution.md
(Variant B — warn-and-skip), then ingest the single paper that was read:
if [ -d research-wiki/ ]; then
cd "$(git rev-parse --show-toplevel 2>/dev/null || pwd)" || exit 1
ARIS_REPO="${ARIS_REPO:-$(awk -F'\t' '$1=="repo_root"{print $2; exit}' .aris/installed-skills.txt 2>/dev/null)}"
WIKI_SCRIPT=".aris/tools/research_wiki.py"
[ -f "$WIKI_SCRIPT" ] || WIKI_SCRIPT="tools/research_wiki.py"
[ -f "$WIKI_SCRIPT" ] || { [ -n "${ARIS_REPO:-}" ] && WIKI_SCRIPT="$ARIS_REPO/tools/research_wiki.py"; }
[ -f "$WIKI_SCRIPT" ] || {
echo "WARN: research_wiki.py not found; paper summary delivered, wiki ingest skipped. Fix: bash tools/install_aris.sh, export ARIS_REPO, or cp <ARIS-repo>/tools/research_wiki.py tools/." >&2
WIKI_SCRIPT=""
}
[ -n "$WIKI_SCRIPT" ] && python3 "$WIKI_SCRIPT" ingest_paper research-wiki/ \
--arxiv-id "<paper_arxiv_id>" \
[--thesis "<one-line thesis from the Tier 1 overview>"]
fiThe helper handles metadata fetch, slug, dedup, page creation, index
rebuild, and log append — do not handwrite papers/<slug>.md. See
shared-references/integration-contract.md.
If wiki was not present at read time (or the helper was unreachable),
the user can backfill via
python3 "$WIKI_SCRIPT" sync research-wiki/ --arxiv-ids <id> after
resolving $WIKI_SCRIPT as above.
Key Rules
- Overview first:
overviewis the fastest path and must always be tried before deeper tiers. Only escalate when needed. - Minimal reads: At
srctier, read only the files that answer the question. Full-tree reads waste tokens. - Cross-platform: When downloading and extracting the source archive, prefer cross-platform approaches (e.g., Python stdlib) over platform-specific commands to ensure Windows/WSL compatibility.
- No PDF parsing: This skill reads structured markdown and LaTeX source, not raw PDFs. For PDF content, suggest
/arxivwith download. - Rate limiting: arXiv source download may rate-limit. If HTTP 429 occurs, wait 5 seconds and retry once. If still blocked, report the error and suggest
/deepxivas alternative. - Complementary, not competing: This skill complements
/arxiv(search + download) and/deepxiv(progressive reading). Do not re-implement their functionality.
Integration with Other Skills
As enrichment in /research-lit
/research-lit can use this skill's Tier 1 (overview) as a fast enrichment step between search and deep analysis. After finding arXiv papers in Step 1, fetch AlphaXiv overviews to quickly assess relevance before committing to full-text reads:
Step 1: Search → list of arXiv IDs
Step 1.5: AlphaXiv overview for top 5-8 papers (this skill, Tier 1 only)
Step 2: Deep analysis only for papers that pass the relevance filterThis saves significant tokens by filtering out marginally relevant papers before deep reading.
As follow-up from other skills
After /research-lit, /novelty-check, or /idea-discovery surface a specific paper, users can invoke /alphaxiv PAPER_ID for a fast deep-dive without re-running the full survey.
Other versions5 projects use a version of this.
Word for word · 1
- Chanw-research/claude-code-paper-writing★ 42100% same
Edited · 3
- wanshuiyin/Auto-claude-code-research-in-sleep★ 18k79% same
- Immortalqx/my_codex_skills★ 5488% same
- talhaMah56/claude_skills★ 081% same
Wrote their own version · 1
- Agents4Academia-AI/UReKA★ 9same 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 repository84 other files it gives its agents.
- skills/rules/common/agents.mdAGENTS.md
- skills/rules/zh/agents.mdAGENTS.md
- ablation-plannerSkill
- analyze-resultsSkill
- arxivSkill
- auto-paper-improvement-loopSkill
- auto-review-loop-llmSkill
- auto-review-loop-minimaxSkill
- auto-review-loopSkill
- citation-auditSkill
- claims-draftingSkill
- comm-lit-review-claude-singleSkill
- deepxivSkill
- dse-loopSkill
- embodiment-descriptionSkill
- exa-searchSkill
- experiment-auditSkill
- experiment-bridgeSkill
- experiment-planSkill
- experiment-queueSkill
- feishu-notifySkill
- figure-descriptionSkill
- figure-specSkill
- formula-derivationSkill
- gemini-searchSkill
- grant-proposalSkill
- idea-creatorSkill
- idea-discovery-robotSkill
- idea-discoverySkill
- invention-structuringSkill
- jurisdiction-formatSkill
- kill-argumentSkill
- mermaid-diagramSkill
- meta-optimizeSkill
- monitor-experimentSkill
- novelty-checkSkill
- openalexSkill
- overleaf-syncSkill
- paper-claim-auditSkill
- paper-compileSkill
- paper-figureSkill
- paper-illustration-image2Skill
- paper-illustrationSkill
- paper-planSkill
- paper-posterSkill
- paper-slidesSkill
- paper-talkSkill
- paper-writeSkill
- paper-writingSkill
- patent-novelty-checkSkill
- patent-pipelineSkill
- patent-reviewSkill
- pixel-artSkill
- prior-art-searchSkill
- proof-checkerSkill
- proof-writerSkill
- qzcliSkill
- rebuttalSkill
- research-litSkill
- research-pipelineSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

