Menu
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.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Write and publish a new blog post for the skillfold site (site/blog/). Use whenever asked to write a blog post, cover a news story about the agent tooling ecosystem, announce a feature rollout, publish the next post from the queue, or when the weekly blog automation runs. Covers the full pipeline - finding the story, verifying it against primary sources, writing the markdown post, regenerating the site, and shipping the PR.
Review code for correctness, clarity, and security.
Write clean, correct, production-quality code.
Evaluate trade-offs, document options, and justify recommendations.
Read, create, edit, and organize files and directories.
Work with GitHub branches, PRs, issues, and reviews via the gh CLI.
| 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. |
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.
skillfold.yaml at the project root:
skills:
commit-helper: ./skills/commit-helper # local directory
frontend-design: github:owner/repo/path/to/skill@v1.2.0 # GitHub (tag, branch, or SHA)
planning: npm:skillfold/planning@2.0.0 # npm package
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.
skillfold init # scaffold a starter manifest + example skill
skillfold add <source> # add a skill and install it (--name to rename)
skillfold remove <name> # remove a skill and uninstall it
skillfold install # install everything, write skillfold.lock
skillfold install --frozen # CI mode: exact lockfile install, fail on drift
skillfold update [name...] # re-resolve moving refs, then reinstall
skillfold check # verify manifest, lockfile, and installed files agree
skillfold list # status table (ok / modified / not installed / not locked)
skillfold info <name> # source, pin, hash, and install path for one skill
skillfold search [query] # find skill packages on npm
Add -g / --global to manage ~/.claude/skills instead of the project.
skillfold.yaml and skillfold.lock. Never edit the lockfile by hand.@ref in the manifest (or run skillfold update <name>), then run skillfold install..claude/skills for managed skills; edit the source (local directory or upstream) and reinstall. skillfold list shows modified when installed files drifted.check fails in CI, the fix is almost always skillfold install locally and committing the resulting lockfile.skillfold add npm:<package>/<skill> for published skills; the skillfold package itself ships general-purpose skills (planning, research, code-review, testing, and more).