skills-stack
CLAUDE.md2 starsChanged 3 months agoMITView on GitHub
A curated inventory of agent skills and plugins, not a codebase. README.md catalogs each skill grouped by creator with links to upstream source repos, and install.sh installs them fresh from upstream via npx skills add. The only exception is skills/ — the owner's own skills, vendored here so this repo is itself an installable source (npx skills add cranberrii/skills-stack). When adding or removing a skill source, update both: 1. the repo list in install.sh 2. the corresponding section/table and the…
In this repository2 other files it gives its agents.
- codebase-catch-upSkill
- explain-diff-htmlSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
When adding or removing a skill source, update both:
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this repo is
A curated inventory of agent skills and plugins, not a codebase. README.md catalogs each skill grouped by creator with links to upstream source repos, and install.sh installs them fresh from upstream via npx skills add. The only exception is skills/ — the owner's own skills, vendored here so this repo is itself an installable source (npx skills add cranberrii/skills-stack).
The files that matter
README.md— the catalog. Skills grouped by creator, one table per source repo.install.sh— loops over the source repos (including this one) and runsnpx skills add <repo> "$@"(extra args like-a claude-codepass through to target specific agents).skills/<name>/SKILL.md— the vendored own-skills. Adding one here means adding a row to the README's "My skills" table.
Keeping them in sync
When adding or removing a skill source, update both:
- the repo list in
install.sh - the corresponding section/table and the "pick individual sources" command list in
README.md
Claude Code plugins (superpowers, feature-dev, ponytail, etc.) install via /plugin install, not the skills CLI — they belong only in the README's plugin sections, not in install.sh.
Testing
There is no build or test suite. To verify install.sh changes: bash -n install.sh for syntax; actually running it installs skills into the user's agent config dirs.
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.