← ClaudeAtlas

smlisted

Manage the local SM skill registry, Producer-owned skill artifacts, Agent grants, immutable projections, and the Svelte dashboard. Use when an agent needs to inspect, add, generate, update, publish, authorize, build, apply, verify, or troubleshoot skills governed by ~/.sm for Codex, Claude, or Pi, or when the user asks to open or show the skill-management page so they can inspect or operate it themselves.
yansircc/skill-manager · ★ 0 · Web & Frontend · score 65
Install: claude install-skill yansircc/skill-manager
# SM Treat `~/.sm` as the only editable registry and committed Git state as the only projection input. ```text Producer repo -> external artifact -> ~/.sm/skills -> consumer generation -> Agent ``` ## Preserve the boundaries - Edit a generated skill in its Producer repo, then run `sm update`; never edit its canonical copy. - Edit an unowned skill only in `~/.sm/skills/<id>`. - Keep Producer repos unaware of `sm`, `~/.sm`, and Agent discovery paths. `make skill` must only create an external artifact. - Define generated ownership once in `~/.sm/producers/<id>.json`. One Skill ID has exactly one Producer. - Build consumer projections only from committed `~/.sm` state. Review and commit CLI-produced catalog changes before building. - Do not restore the removed arbitrary-root `scan`, `adopt`, or `publish --id <path>` workflows. ## Inspect before changing ```sh git -C ~/.sm status --short sm producers --repo ~/.sm sm scan --repo ~/.sm --json ``` Treat `new`, `updated`, `conflict`, and `invalid` as distinct facts. Do not publish through conflicts or invalid artifacts. ## Relocate a Producer When a Producer repository moves, update its locator explicitly: ```sh sm producer relocate --repo ~/.sm <producer-id> <new-root> ``` Require a clean SSOT. The command runs the existing build in `new-root`, validates the complete declared Skill set, and commits only `producers/<id>.json`. It does not publish artifacts or rebuild Agent generations. Run `sm update` separately only when t