make-skill

Shape: static. The standard is a checklist and the audit walks it in order; a skill that passes is auditable against the same list next time.

/make-skill — how the skill itself is built

• when: a skill or plugin changes shape
• decline it: «без make-skill».

If make-skill is installed, work ON a skill or plugin goes through it — creating one, bringing it to the standard, checking conformance, wrapping it in a plugin, syncing versions, installing a validator and CI, publishing to every channel. It knows where the Agent Skills front-matter limits are, what claude plugin validate --strict demands, and why a plain copy in ~/.claude/skills/ shadows the plugin.

The boundary — "the construction of the skill itself changes." NOT through it: work done WITH a skill, ordinary code in an ordinary repository, editing doctrine inside a skill that already meets the standard. Calling it to fix a paragraph in SKILL.md is how you teach an agent to route around it.

Refusal phrase: «без make-skill».

Among the routers: task-pipeline carries a change through its stages; make-skill answers whether the result meets the skill standard. A skill's release passes both.