skill-library
Skill8 starsChanged 39 days agoMITView on GitHub
Your library of skills made by source-to-skill - lists every video, course, podcast, paper, book, article, docs and repo skill installed for Claude Code, Codex, Copilot, Gemini and other agents, finds which one covers a question, flags skills whose playlist, channel, feed or docs has moved on, and refreshes them. Use when the user runs /skill-library, or asks "what skills do I have", "which of my skills covers X", "what did I learn about X", "are any of my skills out of date", "refresh all my skills", or wants to merge overlapping skills.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Mathews-Tom/armorytheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Mathews-Tom/armory★ 340same 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 repository4 other files it gives its agents.
- docs/llms.txtllms.txt
- skill-evalSkill
- skill-studySkill
- source-to-skillSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Distinctive: line 8
Run from this skill's directory:
- Very specific: line 45
When two or more skills cover the same topic (overlapping descriptions, same author or course), offer to build one topic skill from their …
≈ “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
skill-library
Run from this skill's directory:
python3 scripts/library.pyIt prints JSON: every skill folder with a source.json (or, for topic
skills, sources/*.source.json) under the agents' user and project skills
folders, with its description, sources, age, and refresh_due. It reads
only; pass --root <dir> for another folder and --stale-days N to change
the 30-day refresh threshold.
List
Show a compact table: name, type, title, extracted (date), tokens, and a
mark on refresh_due skills. Group by source type when there are more than
ten. No skills found → say where you looked and suggest
/source-to-skill <url-or-file>.
Find
For "which skill covers X": match X against each skill's description first,
then open only the matching skills' SKILL.md indexes. Answer with the
skill name, the support file, and the deep link or section where X is
covered, then answer the question itself from that file. Name every skill
that covers X when several do; when they disagree, show both positions
side by side.
Refresh
refresh_due marks playlists, channels, podcast feeds, docs sites, repos,
threads and notes folders extracted 30 or more days ago. Before refreshing,
list them with their age and ask which to refresh. For each one the user
picks, follow the source-to-skill skill's "Refresh an existing skill"
steps with that skill directory. Run YouTube re-extractions one at a time,
never in parallel: YouTube rate-limits a machine that asks too often.
Merge
When two or more skills cover the same topic (overlapping descriptions,
same author or course), offer to build one topic skill from their
source.json origins with /source-to-skill <source> <source> ... <slug>.
The old skills stay until the user deletes them; never delete a skill
yourself.
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.

