agentleFS
lyh843lyh843/AgentSkills/skills/ai-paper-digest/SKILL.md

ai-paper-digest

Skill1 starsChanged 5 months agoMITView on GitHub

Collect and summarize recent AI papers with emphasis on major ML/AI venues, journals, arXiv, and paper-discovery sites. Use when Codex needs to build a daily or topical AI paper digest, rank papers from venues such as ICML/NeurIPS/ICLR/CVPR/AAAI/KDD, give short Chinese introductions, or continue with follow-up analysis of a specific paper's methods, contributions, experiments, and limitations.

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 13 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    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
  1. Distinctive:

    Use this skill to produce a compact, source-aware AI paper briefing first, then continue into deeper paper analysis on demand.

    line 8
  2. Distinctive:

    Use references/source-priority.md to decide which venues and sites to prioritize for the user's request.

    line 12
  3. Distinctive:

    When the user points to one paper for deeper analysis, switch from digest mode to paper-analysis mode and work from the paper abstract, …

    line 17
  4. Very specific:

    Use daily-digest when the user wants today's or recent papers across sources.

    line 22
  5. Very specific:

    Use venue-focused when the user cares about conferences or journals such as ICML, NeurIPS, ICLR, CVPR, COLT, TPAMI, or TMLR.

    line 23
  6. Very specific:

    Use single-paper-analysis when the user asks about one named paper, one link, one PDF, or a follow-up such as "这篇论文的方法是什么".

    line 24
  7. Distinctive:

    Treat the user's preferred venues as a ranking hint, not a reason to ignore fresher relevant papers from other sources.

    line 33
  8. Distinctive:

    Prefer official or primary sources when available.

    line 34
  9. Distinctive:

    Keep each paper entry compact unless the user asks for depth.

    line 38
  10. Distinctive:

    If "today" is ambiguous because a source updates weekly or irregularly, say the exact time basis, for example "近 24 小时 arXiv" or "近 7 …

    line 45
  11. Very specific:

    If a local PDF is provided, use $grounded-file-qa for evidence-grounded reading and page-aware follow-ups.

    line 53
  12. Distinctive:

    Use the venue registry in references/source-priority.md.

    line 65
  13. Distinctive:

    Use this script for a reusable, dependency-light first pass over recent AI papers.

    line 77
  14. Distinctive:

    Do not overclaim novelty or results if only titles or abstracts are available.

    line 99
  15. Distinctive:

    If a source is temporarily unavailable, say which source failed and continue with the remaining sources.

    line 102
  16. Distinctive:

    If a venue page is difficult to scrape, fall back to discovery sites or search, then verify the target paper page before summarizing.

    line 103
  17. Distinctive:

    If the user asks for "today's hottest" papers, explain the ranking basis because there is no single authoritative AI-wide hotness metric.

    line 104

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AI Paper Digest

Use this skill to produce a compact, source-aware AI paper briefing first, then continue into deeper paper analysis on demand.

Quick Start

  • For a daily digest, run scripts/fetch_ai_digest.py to collect recent papers from arXiv, OpenAlex journals, and selected paper-discovery feeds.
  • Use references/source-priority.md to decide which venues and sites to prioritize for the user's request.
  • Return a short Chinese introduction for each paper:
    1. what the paper studies
    2. the core idea or method at a high level
    3. why it may matter
  • When the user points to one paper for deeper analysis, switch from digest mode to paper-analysis mode and work from the paper abstract, official page, PDF, or local file.

Workflow

1. Decide the task mode

  • Use daily-digest when the user wants today's or recent papers across sources.
  • Use venue-focused when the user cares about conferences or journals such as ICML, NeurIPS, ICLR, CVPR, COLT, TPAMI, or TMLR.
  • Use single-paper-analysis when the user asks about one named paper, one link, one PDF, or a follow-up such as "这篇论文的方法是什么".

2. Build the source set

  • Default priority order:
    1. arXiv daily preprints for freshness
    2. Hugging Face Papers for community-visible daily papers
    3. OpenAlex journal results for recent journal articles
    4. Official proceedings or venue pages for venue-specific retrieval
    5. Secondary discovery sites such as Aminer, Paper Copilot, Bohrium for navigation and triangulation
  • Treat the user's preferred venues as a ranking hint, not a reason to ignore fresher relevant papers from other sources.
  • Prefer official or primary sources when available. Use discovery sites to locate papers faster, then link back to the paper page, proceedings page, arXiv page, DOI page, or PDF.

3. Produce the digest

  • Group or tag papers by venue family where possible: core ML, theory, vision, broad AI, data mining, journals, or community picks.
  • Keep each paper entry compact unless the user asks for depth.
  • Include:
    • title
    • source and venue guess
    • date or recency basis
    • paper link
    • 2-4 sentence Chinese introduction
  • If "today" is ambiguous because a source updates weekly or irregularly, say the exact time basis, for example "近 24 小时 arXiv" or "近 7 天期刊文章".

4. Continue into single-paper analysis

  • For a follow-up on one paper, gather the best available source in this order:
    1. local PDF or local note from the user
    2. official abstract or proceedings page
    3. arXiv abstract or PDF
    4. publisher abstract page
  • If a local PDF is provided, use $grounded-file-qa for evidence-grounded reading and page-aware follow-ups.
  • For method analysis, structure the answer with:
    1. problem setting
    2. proposed method
    3. model or algorithm components
    4. training or optimization strategy
    5. experiments and findings
    6. limitations or assumptions
  • Separate direct evidence from inference. If the method cannot be confirmed from the abstract alone, say that and request or fetch the PDF before going deeper.

Venue Coverage

Use the venue registry in references/source-priority.md. The main target set includes:

  • Core ML: ICML, NeurIPS, ICLR
  • Theory: COLT, AISTATS
  • Vision: CVPR, ICCV, ECCV
  • Broad AI: AAAI, IJCAI
  • Data mining: KDD, ICDM
  • Journals: IEEE TPAMI, IEEE TKDE, JMLR, Machine Learning, Artificial Intelligence, TMLR
  • Additional sources: arXiv, Hugging Face Papers, Aminer, Paper Copilot, Bohrium, Hugging Face Blog

Scripts

scripts/fetch_ai_digest.py

  • Use this script for a reusable, dependency-light first pass over recent AI papers.
  • It fetches:
    • recent arXiv AI/ML categories
    • recent OpenAlex journal articles filtered for AI-related topics
    • Hugging Face Papers page headlines
  • It ranks results with simple heuristics and prints JSON, so the result can be reformatted into markdown or fed into later analysis steps.

Example:

python3 skills/ai-paper-digest/scripts/fetch_ai_digest.py --days 3 --limit 20

When to skip the script

  • Skip the script if the user already provided a specific paper or PDF.
  • Skip the script if the task is only to explain one known paper.
  • Skip the script if the environment blocks network and no cached or local sources are available.

Response Style

  • Answer in Chinese unless the user asks otherwise.
  • For digest entries, optimize for scanability and avoid long abstracts pasted verbatim.
  • For deeper paper analysis, use clear headings and concise technical language.
  • Do not overclaim novelty or results if only titles or abstracts are available.

Failure Handling

  • If a source is temporarily unavailable, say which source failed and continue with the remaining sources.
  • If a venue page is difficult to scrape, fall back to discovery sites or search, then verify the target paper page before summarizing.
  • If the user asks for "today's hottest" papers, explain the ranking basis because there is no single authoritative AI-wide hotness metric.

Prompt Patterns

  • Use $ai-paper-digest to give me today's AI papers with short Chinese intros.
  • Use $ai-paper-digest to focus on ICLR, NeurIPS, ICML, and arXiv papers from the last 3 days.
  • Use $ai-paper-digest to find recent CVPR and ICCV related papers and tell me which ones are worth reading first.
  • Use $ai-paper-digest to summarize this paper first, then explain its method and experiments.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.