writing-praxis-skilllisted

# writing-praxis-skill ## Overview A new praxis skill needs a SKILL.md that the Claude Code plugin runtime can parse and route correctly. Without a consistent structure, the runtime silently misroutes or truncates the description, and contributors have to reverse-engineer the pattern from the existing specs. **Core principle:** one skill = one responsibility. If a skill needs a second trigger phrase to describe a second job, split it into two skills. ## When to Use - Creating a new praxis skill from scratch - Reviewing an existing SKILL.md for structural compliance - Onboarding a contributor who will add a skill ## Process ### Step 1: Copy the Template ```bash cp skills/SKILL.md.tmpl skills/<skill-name>/SKILL.md ``` ### Step 2: Fill in the Frontmatter Replace every `<...>` placeholder. Do not leave any placeholder text in the committed file. ```yaml --- name: <skill-name> # kebab-case; must match the directory name description: > <One-line description of what the skill does.> when_to_use: > Triggers on "<keyword1>", "<keyword2>", "<Korean-keyword>". --- ``` **Rules:** - `name` must exactly match the directory name under `skills/`. - `description` says what the skill does — concise, scannable, and with no trigger phrases in it. - `when_to_use` holds the `Triggers on "..."` clause, plus any `Do NOT activate on "..."` exclusion. The runtime appends it to `description` in the skill listing (<https://code.claude.com/docs/en/skills.md>), so routing