core-skills
CLAUDE.md0 starsChanged 5 months agoMITView on GitHub
panel, synthesize, and tdd are vendored into the auto-task plugin (~/github/auto-task) so it stays self-contained. If you change any of these three here, re-vendor them into auto-task afterwards — otherwise auto-task's copies go stale. The re-vendor recipe lives in ~/github/auto-task/CLAUDE.md (copy the dir, then rewrite /core-skills: → /at:, then bump auto-task's version and refresh it). The other skills in this plugin are not vendored anywhere. Skills invoke each other via the /core-skills:<skill> namespace. A few skills (ingest-design, create-design-brief, panel, sop)…
In this repository13 other files it gives its agents.
- clean-codeSkill
- create-design-briefSkill
- dddSkill
- goosSkill
- ingest-designSkill
- kaizenSkill
- panelSkill
- researchSkill
- review-loopSkill
- software-designSkill
- sopSkill
- synthesizeSkill
- tddSkill
The file
Files
CLAUDE.md — Core-Skills Plugin
Panel, Synthesize, Tdd Are Vendored Downstream
panel, synthesize, and tdd are vendored into the auto-task plugin (~/github/auto-task) so it stays self-contained. If you change any of these three here, re-vendor them into auto-task afterwards — otherwise auto-task's copies go stale. The re-vendor recipe lives in ~/github/auto-task/CLAUDE.md (copy the dir, then rewrite /core-skills: → /at:, then bump auto-task's version and refresh it).
The other skills in this plugin are not vendored anywhere.
Internal Skill References
Skills invoke each other via the /core-skills:<skill> namespace. A few skills (ingest-design, create-design-brief, panel, sop) reference /at:* skills — the task-lifecycle lives in the auto-task plugin — so those refs resolve only when auto-task is also enabled.
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.