digest
Skill0 starsChanged 6 days agoMITView on GitHub
Periodic "what's new and worth it" scan across GitHub, Hugging Face, npm, PyPI, Docker Hub, VS Code/Open VSX, MCP registries and the Roblox Creator Store for the user's interests, skipping anything already reviewed, and flagging new releases of things already installed. Good as a weekly scheduled task. Use for "what's new", "weekly digest", "scout tools", /vetted:digest [topic].
36 other projects use a version of this.
Adopted by
Most recently taken up by
- Liam-coding/SelfOStheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- zaynram/scholartheir own version, first seen Nov 8, 2026
- Jasenpan1987/multi-codetheir own version, first seen Nov 8, 2026
- zalogarcia/zalo-claude-code-setuptheir own version, first seen Nov 8, 2026
- PromptPotter/prompt-potter-optimizertheir own version, first seen Nov 8, 2026
Used with
Projects with it also use aeon-update, auto-workflow and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
aaronjmarsSkillaeon-update
Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.
Also in 4 projects that use this
- aaronjmarsSkill
auto-workflow
Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.
Also in 4 projects that use this
- +10 more from aaronjmars
Other versions36 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 36
- anthropics/knowledge-work-plugins★ 36ksame name
- aaronjmars/aeon★ 789same name
- aeonfun/aeon★ 789same name
- markmhendrickson/neotoma★ 38same name
- jexchan/dailyup-second-brain-starter★ 33same name
- norrietaylor/distillery★ 25same name
- wrg32786/aigent-os★ 25same name
- aaronjmars/miroshark-aeon★ 20same name
- MiroShark/miroshark-aeon★ 20same name
- Treasoni/kaoyan_skills★ 19same name
26 more not listed
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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read ~/.claude/vetted-interests.md (one topic | sources per line).
“Common” is measured: kept by at least 6 in 10 of the 32 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
Digest
Read ${CLAUDE_PLUGIN_ROOT}/references/sources.md first.
1. Interests
Read ~/.claude/vetted-interests.md (one topic | sources per line). If it's missing, infer 4-6 topics from the user's recent projects and memory, write the file, and tell them they can edit it. A topic passed as an argument replaces the list for this run.
2. Search
For each topic, search its sources for things created in the last 30 days and for established projects that shipped a notable release. Skip anything already in ~/.claude/vetted-log.md or ~/.claude/vetted-seen.md, anything archived or deprecated, anything unlicensed, and likely typosquats. Keep at most 8 overall.
3. Installed updates
For each entry in vetted-log.md, check for a newer version. List the updates and offer /vetted:report on them. A new version is new code, so it needs vetting again.
4. Report
Table: Name | Source | What | Topic | Why now (new / big release / fast rising) | Verdict (Adopt / Try / Skip). The digest does not scan. Point to /vetted:report or /vetted:find before anything gets installed. Append every reviewed row to vetted-seen.md as - <source>:<name> — verdict — <date>.
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.