skill-authoringlisted

# Skill Authoring > **Style:** Mode-B-lite. Clean-room, Fusebase-specific procedure for deciding, writing, wiring, and validating reusable skills. ## Purpose Create or update skills without skill sprawl, role drift, mirror drift, or license contamination. This skill governs reusable instruction capture: what deserves a skill, where it belongs, which role uses it, and what validation proves it was authored cleanly. ## When to invoke - Operator asks to create, update, install, import, compare, or analyze a skill. - Operator provides an external skill, prompt, guide, or workflow and asks to reproduce similar capability in Fusebase Flow. - A recurring pattern should become durable reusable expertise. - Existing skill behavior needs tightening after a missed bug, failed handoff, or repeated role drift. - A framework skill is added or changed and provider mirrors/manifests must stay in sync. ## Do not invoke when - The request is normal per-ticket implementation covered by `implementation-planning`, `validation-and-qa`, or another domain skill. - The issue is a one-off failure with a concrete cause; file `docs/problem-catalog/<slug>/problem.md` instead. - The operator wants to copy external text verbatim. Refuse copying and offer clean-room capability extraction. - The topic is already covered by an existing skill and only needs normal use, not authoring or update. - A provider mirror is the only target. Canonical skill edits start in `skills/` or `docs/skills/`; mirrors are