manage-skillslisted

Inspect and edit the skills already on this machine — list, add, remove, edit, search, copy between scopes, or set up the directories. Use on 'manage skills', 'local skills', 'add skill', 'remove skill', 'edit skill', 'welche Skills habe ich', 'Skill anlegen'. This is local CRUD; to find a skill in a marketplace use `search-skills` or `install-skill`, to write a good one use `author-skills`.
juliuswiener/nord-kit · ★ 0 · AI & Automation · score 65

Install: claude install-skill juliuswiener/nord-kit

# manage-skills — local skill CRUD Skills are plain directories holding a `SKILL.md` with YAML frontmatter. | scope | path | precedence | |---|---|---| | user | `~/.claude/skills/<slug>/SKILL.md` | enterprise > user > project | | project | `.claude/skills/<slug>/SKILL.md` | committed with the repo | | plugin | `<plugin>/skills/<slug>/SKILL.md` | namespaced `plugin:skill`, cannot collide | ## Subcommands ``` list table of all skills by scope add [slug] interactive creation wizard remove <slug> confirm-gated deletion edit <slug> field-level interactive edit search <query> ranked full-text search over name, description and body info <slug> full detail for one skill sync copy across scopes, showing the diff first setup guided first-time wizard scan quick inventory, no wizard ``` ### list Scan both scopes, parse each frontmatter, print one section per scope with `name · description · scope`, then a one-line summary (`3 user | 2 project | 5 total`). Show `N/A` for a field that is missing rather than omitting the row — an unparseable SKILL.md is the thing worth seeing. ### add Ask in one message: slug (lowercase and hyphens only, no spaces), one-line description, scope, and whether it has side effects. Then write the scaffold, report the path, and say it activates at the next session start. ```yaml --- name: <slug> description: "<what it does. Then: use when …, or when th