deepxiv-trending-digest
Skill843 starsChanged 8 months agoMITView on GitHub
Summarize recent hot academic papers using deepxiv trending, brief, head, and section reads, then produce a markdown digest highlighting what each paper is about and which papers deserve deeper reading.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- amaxz/hermes-skillsword for word, first seen May 10, 2026
Other versions1 project uses a version of this.
Word for word · 1
- amaxz/hermes-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository17 other files it gives its agents.
- deepxiv-baseline-tableSkill
- deepxiv-cliSkill
- deepxiv-fa-appraiseSkill
- deepxiv-fa-casesSkill
- deepxiv-fa-cveSkill
- deepxiv-fa-drugsSkill
- deepxiv-fa-filingsSkill
- deepxiv-fa-frSkill
- deepxiv-fa-grantsSkill
- deepxiv-fa-lawSkill
- deepxiv-fa-osvSkill
- deepxiv-fa-standardsSkill
- deepxiv-fa-stocksSkill
- deepxiv-fa-talentSkill
- deepxiv-fa-trialsSkill
- deepxiv-fa-uk-eu-lawSkill
- deepxiv-fa-us-lawSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. About 0 are common, 13 are distinctive, and 13 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.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when the user wants a recent hot-paper roundup, trending paper summary, weekly paper digest, or a markdown report based on …
- Very specific: line 18
Read only the most relevant sections with deepxiv paper <id> --section ...
- Very specific: line 19
Write a clean .md summary with recommendations
- Distinctive: line 25
Start with a small, recent set unless the user asks otherwise.
- Very specific: line 32
Use --days 7 for "recent hot papers"
- Very specific: line 33
Use --limit 10 for a manageable first pass
- Very specific: line 34
If the user asks for a broader roundup, use --days 14 or --days 30
- Very specific: line 53
Do not jump to full text yet.
- Distinctive: line 57
After reading briefs, choose the top 1-3 papers for deeper inspection.
- Distinctive: line 67
If a paper sounds incremental, unclear, or out of scope, keep it in the digest but skip deep reading.
- Very specific: line 77
Use --head to decide whether to drill down and which section matters most.
- Distinctive: line 79
Look for sections such as:
- Distinctive: line 85
Prefer section reads over full paper reads.
- Distinctive: line 89
Read at most 1-2 sections per paper unless the user explicitly asks for a deep dive.
- Very specific: line 100
Read Introduction if the contribution is still fuzzy
- Very specific: line 101
Read Method if the core idea matters
- Very specific: line 102
Read Results if the claim sounds strong and needs verification
- Very specific: line 103
Read Limitations or Discussion if tradeoffs matter
- Distinctive: line 109
Write a markdown file in the current workspace unless the user gave a different path.
- Distinctive: line 173
Keep the digest skimmable
- Distinctive: line 174
Prefer short paragraphs and flat bullets
- Distinctive: line 178
Do not pretend to have verified claims you have not checked
- Distinctive: line 182
If briefs are enough for the user's request, stop there
- Very specific: line 183
Use --head only for the most promising papers
- Very specific: line 184
Use --section only after --head suggests a high-value section
- Distinctive: line 185
Do not read full paper markdown unless the user explicitly asks for a full analysis
≈ “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
DeepXiv Trending Digest
Use this skill when the user wants a recent hot-paper roundup, trending paper summary, weekly paper digest, or a markdown report based on DeepXiv trending papers.
Goal
Turn recent DeepXiv trending papers into a concise markdown digest:
- Find currently hot papers with
deepxiv trending - Brief each candidate with
deepxiv paper <id> --brief - Select the most promising papers for deeper inspection
- Inspect structure with
deepxiv paper <id> --head - Read only the most relevant sections with
deepxiv paper <id> --section ... - Write a clean
.mdsummary with recommendations
Default Workflow
1. Pull trending papers
Start with a small, recent set unless the user asks otherwise.
deepxiv trending --days 7 --limit 10 --jsonDefault heuristics:
- Use
--days 7for "recent hot papers" - Use
--limit 10for a manageable first pass - If the user asks for a broader roundup, use
--days 14or--days 30
2. Brief every candidate
For each selected arXiv ID, fetch a brief first:
deepxiv paper <arxiv_id> --briefCapture:
- title
- arXiv ID
- publish date
- keywords
- TLDR
- citations if present
- GitHub URL if present
Do not jump to full text yet. --brief is the default screening step.
3. Rank for deeper reading
After reading briefs, choose the top 1-3 papers for deeper inspection.
Use signals like:
- strong novelty or surprising result
- practical relevance
- likely user interest
- unusually clear contribution
- useful code release
- especially strong social or research momentum
If a paper sounds incremental, unclear, or out of scope, keep it in the digest but skip deep reading.
4. Inspect paper structure
For the chosen papers:
deepxiv paper <arxiv_id> --headUse --head to decide whether to drill down and which section matters most.
Look for sections such as:
- Introduction
- Method / Approach / Framework
- Experiments / Results / Evaluation
- Discussion / Limitations
Prefer section reads over full paper reads.
5. Read only high-value sections
Read at most 1-2 sections per paper unless the user explicitly asks for a deep dive.
Examples:
deepxiv paper <arxiv_id> --section Introduction
deepxiv paper <arxiv_id> --section Method
deepxiv paper <arxiv_id> --section ResultsSelection guidance:
- Read
Introductionif the contribution is still fuzzy - Read
Methodif the core idea matters - Read
Resultsif the claim sounds strong and needs verification - Read
LimitationsorDiscussionif tradeoffs matter
Avoid reading everything.
Markdown Output
Write a markdown file in the current workspace unless the user gave a different path.
Recommended filename:
trending-paper-digest-YYYY-MM-DD.mdRecommended structure:
# Trending Paper Digest
Date: YYYY-MM-DD
Window: Last 7 days
Source: deepxiv trending
## Executive Summary
- 2-4 bullets with the main themes across the trending list
- Mention the 1-3 most promising papers
## Papers Reviewed
### 1. Paper Title (`arXiv:xxxx.xxxxx`)
What it is about:
Short paragraph based mainly on `--brief`.
Why it matters:
- Bullet
- Bullet
Worth deeper reading?
Yes/Maybe/No, with one sentence.
If deeper review was done:
Sections checked:
- Introduction
- Method
Deeper notes:
Short paragraph with the key insight, evidence, or caveat.
### 2. ...
## Recommended Deep Dives
### Paper Title
- Why it stands out
- Which section to read next
- What question it could answer
## Cross-Cutting Trends
- Repeated themes
- Common methods
- Shared limitations or hype signalsWriting Rules
- Keep the digest skimmable
- Prefer short paragraphs and flat bullets
- Separate "what it says" from "whether it is worth deeper reading"
- Be explicit when a conclusion is based only on
--brief - Be explicit when a conclusion is based on
--heador a section read - Do not pretend to have verified claims you have not checked
Decision Rules
- If briefs are enough for the user's request, stop there
- Use
--headonly for the most promising papers - Use
--sectiononly after--headsuggests a high-value section - Do not read full paper markdown unless the user explicitly asks for a full analysis
Minimal Example
deepxiv trending --days 7 --limit 5 --json
deepxiv paper 2603.20639 --brief
deepxiv paper 2603.26221 --brief
deepxiv paper 2603.20639 --head
deepxiv paper 2603.20639 --section IntroductionThen write the digest as markdown and clearly label:
- all reviewed papers
- which papers were only briefed
- which papers received deeper inspection
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.

