local_skill_managementlisted

# local_skill_management — manage fork-local skills through the DB Fork-local skills are canonical in the live engine DB and persist in the local snapshot. Keep the input `SKILL.md` only as an authoring draft; never copy it under `.super-coder/assets/skills/` or edit the engine seed. ## Create or update 1. Write a draft `SKILL.md` in a Planner-owned path. Use flat frontmatter: ```yaml --- name: repo_skill description: State what the skill does and when it fires. category: substrate common: false --- # Procedure Give instructions with observable success conditions. ``` Use a lowercase underscore name. Keep `common: false`: fork-local grants are always explicit. Apply `authoring_syntax` to the description and body. 2. Commit the draft to the catalogue: ```bash sc skill put --file <path/to/SKILL.md> ``` Success prints `DB + snapshot + flat render + skill projections reconciled`. The command requires the launched shell identity to resolve as Planner, creates or updates the DB row, preserves every existing grant, and creates no managed asset copy. An engine-owned name refuses before any write and points to the upstream engine-skill workflow. 3. Grant a new skill explicitly: ```bash sc skill grant <skill_name> <shell>... ``` Naming a standard shell updates its shared flavor pack. Naming a Bespoke shell updates that shell only. Success includes the same persistence receipt. Creation alone gran