- frontend-design
- react-best-practices
- brainstorming
- deploy-runbook
One copy of every Skill, linked into every project.
Collect Skills in one git repo. Link any Skill into any project, then pull once to update them all. No provider plugins or marketplaces.
1Pick public Skill repos
The same Skills, cloned into every repo.
Clone each repo once. Link its Skills anywhere.
One pull updates every linked project.
Each project pulls its own copy, so atlas-web and billing-api end up on different commits of frontend-design, and both copies go into git.
Each source repo is a submodule of one git repo you own. Each project gets a symlink to the Skill, and git ignores the symlink.
A symlink points at the files in your Skills repo, so it shows the new commit once the pull finishes. A copy is its own folder, and a pull never touches it.
- subanthropics/skills3f2a91c
- subvercel-labs/agent-skills0c04547
- subobra/superpowerse81c2d0
- frontend-design
- brainstorming
- test-driven-development
- frontend-design
- react-best-practices
- brainstorming
Commit the Skills you write alongside your code.
Skills you write, and copies you edit, go into the project's git history like any other file. Third-party Skills are symlinks into your Skills repo, and SkillStash lists each one in the project's .git/info/exclude, so git ignores them.
atlas-web/.claude/skills/ ├─ deploy-runbook/ yours · committed ├─ frontend-design │ → ~/Code/agent-skills/anthropics-skills/skills/frontend-design ├─ react-best-practices │ → ~/Code/agent-skills/vercel-labs-agent-skills/skills/… ├─ brainstorming │ → ~/Code/agent-skills/obra-superpowers/skills/brainstorming └─ design-tokens/ copy · committed, a pull never changes it # .git/info/exclude lists the three symlinks
Also in the app
- ⌘K jumps to any Skill, Tag or project
- Search your Skills repo and skills.sh
- Tag a whole repo as you add it
.claudeand.agents- Reinstall what you deleted
- Checks upstream every six hours
- No account. No telemetry