skill-authoring

# Skill Authoring A skill exists to get determinism out of a stochastic system. **Predictability** is the goal, and it means the agent takes the same *process* every run — not that it produces the same output. Every rule below serves that. `docs/PLUGIN-ASSEMBLY-STANDARD.md` already fixes the *structure* a skill body should take. This is about what makes the content inside that structure work. Adapted from `writing-great-skills` in [mattpocock/skills](https://github.com/mattpocock/skills) (MIT), with the invocation section rewritten for how this plugin actually loads skills. ## When To Use - Writing a new skill, or reviewing one in a PR. - A skill fires when it should not, or fails to fire when it should. - A skill behaves differently run to run on the same input. - Deciding whether something should be a skill at all, or a command, or prose in `CLAUDE.md`. ## When Not To Use - For the mechanical checklist — file layout, registration, required sections. That is `docs/PLUGIN-ASSEMBLY-STANDARD.md` and the CI suites. - For writing prompts that are not skills. That is `skill-meta-prompt`. ## Inputs The skill under construction or review, and an honest answer to: what should the agent do differently because this exists? ## Workflow ### Invocation: explicit by default Every shipped command and skill carries `disable-model-invocation: true`. Claude Code therefore keeps Octopus out of model context until the user chooses an `/octo:*` command. This is a hard platform gat...