skill-creator

# /skill-creator — create an IWE skill > **Scope:** create a new skill OR guide an update to an existing skill in `.claude/skills/` or `.kimi/skills/`. > **Not in scope:** full re-scaffold without deleting the old `SKILL.md` first (delete manually, then call `/skill-creator` again); creating a WP; creating a Pack. > **Role:** ad-hoc content-role «Инженер скиллов»; formalize in Pack if ≥3 skills/year. ## When to use - Pilot wants a new skill for a repeated workflow. - A new tool/agent/system needs a Service Clause + Role + SKILL.md. - A skill needs promotion from author repo to `FMT-exocortex-template`. ## Preconditions (checked, not performed) 1. **WP Gate precondition.** The task must be attached to an agreed WP in the weekly plan or explicitly named by the pilot. `/skill-creator` does not conduct the WP Gate ritual itself. 2. **Routing Gate.** Decide target platform (Claude vs Kimi) and level (project vs user). Default: project-level `.claude/skills/` in the author repo. 3. **IntegrationGate hard-check.** `DP.SC.*` and `DP.ROLE.*` must exist in the PACK repo. If not, the skill stops and offers to create them. Bypass only by explicit pilot instruction «пропусти gate» — no code flag. ## Algorithm ### Step 1 — Check WP Gate precondition Look up the current weekly plan (`current/WeekPlan W{N}.md`) or ask: ``` К какому РП привязано создание скилла? ``` If no WP is named and none matches the skill topic → stop: ``` Создание скилла требует согласованного РП. Сначала отк...