ai-paper-highlights
Skill0 starsChanged 3 months agoMITView on GitHub
Summarize a research paper (title or arXiv ID) into bilingual key highlights: contribution, method, results, limitations. 对论文抓取摘要并输出中英双语要点。
In this repository14 other files it gives its agents.
- ai-code-reviewSkill
- ai-cost-estimatorSkill
- ai-news-digestSkill
- ai-tools-radarSkill
- ai-writing-assistantSkill
- embedding-searchSkill
- fine-tuning-decisionsSkill
- llm-evaluationSkill
- llm-security-checklistSkill
- mcp-server-guideSkill
- model-comparisonSkill
- prompt-engineering-playbookSkill
- rag-pipelineSkill
- structured-output-validationSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
If the URL is not arXiv, fetch the paper's landing page / official abstract.
- Distinctive: line 31
If the abstract is unavailable or the page cannot be fetched, say so plainly and do not guess.
- Distinctive: line 48
Prefer the abstract page over a PDF.
- Distinctive: line 49
Do not fabricate numbers — only state results that are actually in the abstract/text.
- Distinctive: line 50
If the user wants depth (method details), offer to fetch the full HTML version and expand.
- Distinctive: line 51
Keep the summary under ~250 words when the user just asks for 要点.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
AI Paper Highlights | 论文要点速览
Turn a research paper (arXiv ID, title, or URL) into a tight bilingual summary of the things that matter: what it proposes, how it works, what it shows, and what it does not solve.
把一篇论文(arXiv ID / 标题 / 链接)提炼成简短的双语要点:提出了什么、怎么做的、结果如何、局限在哪。
When to use | 适用场景
- The user gives a paper link or arXiv ID and asks for a summary / 要点
- The user asks 「这篇论文讲了什么」「有什么最新研究值得关注」
- Comparing or shortlisting papers for deeper reading
Workflow | 工作流程
- Identify the paper — extract the arXiv ID (e.g.
2401.00001) or resolve the title. - Fetch the abstract —
WebFetchhttps://arxiv.org/abs/<id>(or the provided URL). If the URL is not arXiv, fetch the paper's landing page / official abstract. - Extract the essentials:
- 核心贡献 Contribution — the single new idea in one sentence
- 方法 Method — high-level approach, 2–3 bullets, no dense math
- 关键结果 Results — headline numbers / findings
- 局限 Limitations — what the authors acknowledge (from abstract or conclusion)
- 影响 Impact — why it matters / who cares
- Output bilingual — every section has both 中文 and English lines.
- If the abstract is unavailable or the page cannot be fetched, say so plainly and do not guess.
Output format | 输出格式
# 📄 <Paper title> | 论文要点
- **arXiv / 链接**: https://arxiv.org/abs/<id>
- **核心贡献 Contribution**: 一句话 | one sentence
- **方法 Method**:
- ··· | ···
- **关键结果 Results**: ··· | ···
- **局限 Limitations**: ··· | ···
- **一句话点评 TL;DR**: 值得精读吗?| worth a full read? yes/no + whyTips | 提示
- Prefer the abstract page over a PDF; PDFs are slower and harder to parse reliably.
- Do not fabricate numbers — only state results that are actually in the abstract/text.
- If the user wants depth (method details), offer to fetch the full HTML version and expand.
- Keep the summary under ~250 words when the user just asks for 要点.
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.

