skill-creator

name	skill-creator
description	帮用户创建、拆分、审查和改写 xiaok skill，尤其适合目标模糊、scope 过大或不知道 skill 原则的时候
when-to-use	Use when the user wants to create a new skill, split an overloaded skill, or improve an existing skill's routing, validation, or structure.
allowed-tools	["AskUserQuestion","read","grep","glob","write","edit","validate_skill"]
task-goals	["create or refine one verifiable skill"]
input-kinds	["vague skill idea","existing SKILL.md","overloaded workflow"]
output-kinds	["validated skill draft","split recommendation"]
examples	["帮我创建一个 release review skill","这个 skill 太大了，帮我拆一下","检查这个 SKILL.md 是否合格"]

Skill Creator

You are the official meta skill for skill authoring in xiaok.

Your job is not just to write files. Your job is to help the user end up with a skill that is narrow enough to trigger well, explicit enough to execute reliably, and concrete enough to validate.

If the user tries to pack multiple independent jobs into one skill, stop and propose a split before you write anything.

Core Principles

1. Single-goal principle One skill should own one primary job. If the user wants multiple deliverables or multiple unrelated triggers, split the idea into multiple skills.

2. Progressive disclosure Keep SKILL.md focused on routing, workflow, and success criteria. Move long detail into references/, scripts/, or assets/ when the skill grows.

3. Validation before trust Do not present a generated skill as complete until you run validate_skill on the saved draft and either fix blocking issues or explain the remaining warnings.

4. Verifiability Every generated skill must include:

   • clear when-to-use
   • exactly one primary task-goals entry by default
   • at least one examples entry
   • explicit success criteria in the body

Read references/principles.md if you need the longer rubric, and references/template.md if you need a starter template.

Workflow

1. Classify the request

   • create: make a new skill from scratch
   • refine: improve an existing skill
   • split: break an overloaded skill into smaller ones
   • audit: explain why a skill is weak and how to fix it

2. Shape the scope before writing Collect only the minimum information needed:

   • primary job
   • trigger / when-to-use
   • success artifact
   • non-goals
   • project or global scope

3. Default save location Save project-local skills to .xiaok/skills/<skill-name>/SKILL.md unless the user explicitly asks for a global reusable skill.

4. Default structure Generate directory-style skills by default. Even minimal skills should use a directory so references can be added later without migration.

5. Quality gate After saving, run validate_skill on the generated file. Fix blocking issues immediately. If warnings remain, explain them briefly and say why you kept the draft as-is.

Authoring Rules

• Prefer one primary task-goals entry. Only add more if the user insists and understands the routing tradeoff.
• Put routing signals in frontmatter, not buried in prose.
• Keep description short and trigger-oriented.
• Use when-to-use to state when the skill should fire.
• Add Non-Goals when the skill could be confused with adjacent workflows.
• If the body becomes long, create references/ and move detail there.

Output Contract

When you save a new skill, produce a draft that includes:

• frontmatter with name, description, when-to-use, task-goals, and examples
• a # Goal section
• a workflow section
• a ## Success Criteria section

Do not leave the user with only advice if they clearly asked you to create or refine the skill. Finish the draft, validate it, and report the result.