| name | skillfold-cli |
| description | Use skillfold to manage a project's Claude skills. Declare skills in skillfold.yaml, pin them in skillfold.lock, and install them into .claude/skills. |
Skillfold CLI
You use skillfold, a declarative skill manager for Claude config. Projects declare the skills they use in skillfold.yaml; skillfold installs them into .claude/skills and pins exact revisions in skillfold.lock.
Manifest
skillfold.yaml at the project root:
skills:
commit-helper: ./skills/commit-helper
frontend-design: github:owner/repo/path/to/skill@v1.2.0
planning: npm:skillfold/planning@2.0.0
compose:
reviewer:
description: Review code changes together with their tests.
use: [code-review, testing]
A trailing @ref after the last / pins a version. Composed skills concatenate the bodies of the skills they use into one generated skill.
Commands
skillfold init
skillfold add <source>
skillfold remove <name>
skillfold install
skillfold install --frozen
skillfold update [name...]
skillfold check
skillfold list
skillfold info <name>
skillfold search [query]
Add -g / --global to manage ~/.claude/skills instead of the project.
Rules
- Commit both
skillfold.yaml and skillfold.lock. Never edit the lockfile by hand.
- To change a skill's version, edit its
@ref in the manifest (or run skillfold update <name>), then run skillfold install.
- Never edit files under
.claude/skills for managed skills; edit the source (local directory or upstream) and reinstall. skillfold list shows modified when installed files drifted.
- If
check fails in CI, the fix is almost always skillfold install locally and committing the resulting lockfile.
- Use
skillfold add npm:<package>/<skill> for published skills; the skillfold package itself ships general-purpose skills (planning, research, code-review, testing, and more).