Managing Skills
List installed skills
$ kenji listLists skills installed in the current project. Output shows repo-slug/skill-slug for each skill.
Local skills (current folder):
anthropics-skills/mcp-builder
anthropics-skills/design-algorithmic-art
someuser-kenji-registry/agents-prompt$ kenji list --globalLists globally installed skills in the same format.
Remove a skill
$ kenji remove mcp-builder$ kenji remove mcp-builder --globalIf two different repositories both contain a skill with the same name, Kenji shows all matches and asks you to specify the full path:
Multiple installed skills match "mcp-builder":
- anthropics-skills/mcp-builder
- openai-skills/mcp-builder
Specify the full path:
kenji remove anthropics-skills/mcp-builder$ kenji remove anthropics-skills/mcp-builderAfter removal, the parent repo-slug folder is cleaned up automatically if it becomes empty.
Check where a skill came from
$ kenji where mcp-builderShows the skill's install location (repo-slug/skill-slug), source URL, and install type. Pass --json for machine-readable output, or --verbose for full metadata. Use the full path to disambiguate if needed:
$ kenji where anthropics-skills/mcp-builderSearch the registry
$ kenji search reactReturns up to 5 results from the aggregated registry. Use --namespace to filter by author. For broader browsing, use the web registry.
Inspect a registry item
$ kenji info kenji/react-debugWorks with registry names, GitHub repo paths (user/repo), tree URLs, and raw file URLs.
Copy a global skill into the current project
$ kenji use mcp-builder$ kenji use anthropics-skills/mcp-builder --forceCopies the skill from ~/.kenji/skills/<repo-slug>/<skill-slug>/ into .kenji/skills/<repo-slug>/<skill-slug>/, preserving the full folder structure. Does not re-download from the internet. Pass --force to overwrite an existing local copy.