content/skills/academic-skills/alphaxiv/SKILL.md
Look up, summarize, or explain any arXiv paper using alphaxiv.org's AI-generated overviews. Use this skill whenever the user shares an arXiv or alphaxiv URL, pastes a paper ID (e.g. 2401.12345), or asks to summarize, explain, read, or understand a research paper. Trigger even when the user only mentions a paper title or says "what does this paper say", "explain this paper", "give me the key ideas", or "what are the results". Prefer this over reading raw PDFs — it is faster and structured for LLM consumption.
npx skillsauth add bahayonghang/my-claude-code-settings alphaxiv-paper-lookupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Fetch structured AI overviews for arXiv papers. No auth required.
Parse the paper ID from whatever the user provides:
| Input | Paper ID |
| ------------------------------------------ | -------------- |
| https://arxiv.org/abs/2401.12345 | 2401.12345 |
| https://arxiv.org/pdf/2401.12345 | 2401.12345 |
| https://alphaxiv.org/overview/2401.12345 | 2401.12345 |
| 2401.12345v2 | 2401.12345v2 |
| 2401.12345 | 2401.12345 |
curl -s "https://api.alphaxiv.org/papers/v3/{PAPER_ID}"
On platforms without
curl, useWebFetchwith the same URL.
Extract versionId from the JSON response. This is the UUID needed for the next call.
If this returns 404, the paper hasn't been indexed on alphaxiv yet.
curl -s "https://api.alphaxiv.org/papers/v3/{VERSION_ID}/overview/{LANG}"
On platforms without
curl, useWebFetchwith the same URL.
The response contains:
intermediateReport — the machine-readable report (structured text, best for LLM consumption)overview — the full markdown blog post (human-readable)summary — structured summary with fields: summary, originalProblem, solution, keyInsights, resultscitations — list of cited papers with titles and justificationsPrefer intermediateReport when available — it's specifically formatted for machine consumption. Fall back to summary fields if intermediateReport is null.
If the intermediateReport, summary, and overview fields don't contain the specific information the user is asking about (e.g. a particular equation, table, or section), fetch the full paper text:
curl -s "https://alphaxiv.org/abs/{PAPER_ID}.md"
On platforms without
curl, useWebFetchwith the same URL.
This returns the full extracted text of the paper as markdown. Only use this as a fallback — the overview and intermediate report are usually sufficient.
If this returns 404, the full text hasn't been processed yet. As a last resort, direct the user to the PDF at https://arxiv.org/pdf/{PAPER_ID}.
Adapt presentation to user intent:
| User intent | Format |
|---|---|
| "summarize" / "overview" | 3-5 bullet key contributions, then 1-paragraph summary |
| "explain" / "what does it do" | Plain-language explanation, avoid jargon |
| "what are the results" | Lead with metrics from results field, then context |
| "key ideas" / "main points" | Numbered list of 3-5 insights from keyInsights |
| "read this paper" | Full breakdown: problem → method → results → limitations |
Always include paper title and year. Never reproduce the overview blob verbatim — synthesize from intermediateReport or summary fields.
intermediateReport is null: Use summary and overview fields instead.Default: en. Auto-detect the user's language and use the matching code:
| Language | Code |
|---|---|
| English | en |
| French | fr |
| German | de |
| Spanish | es |
| Chinese | zh |
| Japanese | ja |
| Arabic | ar |
| Hindi | hi |
| Portuguese | pt |
Substitute in Step 3: .../overview/{LANG}. If the user writes in Chinese, use zh automatically — do not ask.
development
Use only when the user explicitly asks for swarm, subagents, parallel agents, dynamic workflow, multi-agent orchestration, 多智能体编排, or when the task truly needs coordinated research plus implementation plus review plus verification packets. Do not use for ordinary code review, planning-only work, single-line bugfixes, routine audits, or migrations unless orchestration is requested or at least two independent workflow dimensions are present.
development
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.
development
Plan-first brainstorming workflow that turns an idea into an approved Markdown implementation plan by default. Use when the user wants to brainstorm, design, scope, or plan a feature/spec before implementation. Spark explores project context, asks only blocking questions, writes the plan under the project root's .plannings/YYYY-MM-DD-feature-slug.md path, self-reviews it, and waits for user approval. Create an HTML or visual plan/spec only when the user explicitly asks for HTML, browser-viewable, or visual output; save the paired .html beside the Markdown plan.
development
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.