sources
Skill0 starsChanged 29 days agoMITView on GitHub
Manage the external source list that slop-compost's Track B reads (failure cases, trends, revenue, Korean communities, your own scraper output) - list sources with citation stats, add, remove, edit, enable, or disable one. Use when the user wants to see or change where slop-compost looks for outside signals - e.g. "slop-compost sources", "add a source", "disable failory", "which sources get cited", "출처 목록", "출처 추가", "출처 끄기", "소스 관리".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- ES-92/esctheir own version, first seen Oct 20, 2026
- gabrieldabbah/genesistheir own version, first seen Jul 28, 2026
- kennethleungty/claude-musictheir own version, first seen Apr 10, 2026
- ShawnBaek/kindle-weekly-lettertheir own version, first seen Mar 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- kennethleungty/claude-music★ 23same name
- gabrieldabbah/genesis★ 4same name
- ShawnBaek/kindle-weekly-letter★ 2same name
- ES-92/esc★ 0same name
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 repositoryOne other file it gives its agents.
- compostSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
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
- Very specific: line 15
If the script is missing (No such file), stop and tell the user: "The sources skill needs the compost skill next to it: install the …
- Very specific: line 17
Write user-facing text in the user's language (SLOP_COMPOST_LANG if set).
- Very specific: line 21
New defaults first: Run <CLI> sources list. If it reports new_default_sources, ask once in one line: "N new default sources (ids) - add …
- Very specific: line 33
After a change, show the changed entry and stop.
“Common” is measured: kept by at least 6 in 10 of the 3 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
sources (slop-compost source list)
Arguments: $ARGUMENTS
This skill shares its script with the compost skill. The two skill folders must be siblings (.../skills/compost and .../skills/sources), as they are in the plugin and in a manual install that links both folders into ~/.claude/skills/.
<CLI>means exactlypython3 ${CLAUDE_SKILL_DIR}/../compost/scripts/ledger.py(write it like this so the pre-approved permission rule matches). Each call prints one JSON line;{"error": ...}means show the message and stop or ask again as below.- If the script is missing (
No such file), stop and tell the user: "Thesourcesskill needs thecompostskill next to it: install the slop-compost plugin, or link bothskills/compostandskills/sourcesinto~/.claude/skills/." - The list is
<ledger>/sources.md(ledger =SLOP_COMPOST_HOME, default~/.slop-compost). The script seeds it from the shipped defaults if it does not exist and never overwrites it. - Write user-facing text in the user's language (
SLOP_COMPOST_LANGif set). Ids, field names, and enum values stay in English.
Do
- New defaults first. Run
<CLI> sources list. If it reportsnew_default_sources, ask once in one line: "N new default sources (ids) - add them? (yes / no)", then<CLI> sources sync-defaults yes|no. Then handle the command. - Handle the command (rules: sources.md, section "
sourcessubcommand"):
| user command | do |
list (or no arguments) | Show the list result as a table: id, category, type, enabled, removed/restored, cited, cited in adopted (- = no runs yet). |
add [id] | Ask once, one line: type, how, category (e.g. fetch, https://example.com/rss, trend). Then <CLI> sources add [id] --type "<type>" --how "<how>" --category <category>. On an error listing allowed values, show them and ask again. |
remove <id> | <CLI> sources remove <id> (marks removed, sets enabled: false; nothing is deleted). |
edit <id> | <CLI> sources edit <id> shows the entry. Ask once for field=value pairs on one line, then <CLI> sources edit <id> 'field=value' 'field=value' ... (one quoted argument per pair). id cannot change: suggest remove + add. |
enable <id> / disable <id> | <CLI> sources enable <id> / <CLI> sources disable <id> (enable on a removed entry restores it). |
- An
errorwith the usage line (unknown verb, missing or unknown id): show the usage and the listed ids, then stop. - After a change, show the changed entry and stop. Never edit
sources.mdby hand and never touch files under the skill folders.
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.

