# Skill Creator

Interactive guide for creating, reviewing, and improving agent skills (SKILL.md folders).

- Repository: https://github.com/XiaomiMiMo/MiMo-Code (13741 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add XiaomiMiMo/MiMo-Code --skill skill-creator -g -a claude-code -y`
Codex: `npx skills add XiaomiMiMo/MiMo-Code --skill skill-creator -g -a codex -y`
Cursor: `npx skills add XiaomiMiMo/MiMo-Code --skill skill-creator -g -a cursor -y`
Gemini CLI: `npx skills add XiaomiMiMo/MiMo-Code --skill skill-creator -g -a gemini-cli -y`

## Description

Interactive guide for creating, reviewing, and improving agent skills (SKILL.md folders). Use when the user wants to build a new skill ('create a skill', 'make a skill for X', 'write a SKILL.md', 'turn this workflow into a skill'), review or improve an existing skill, fix a skill that never triggers or triggers too often, or validate a skill folder before sharing it. Do NOT use for general prompt writing, MCP server development, or editing arbitrary markdown files.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Skill Creator

A skill is a folder that teaches an agent how to handle a specific task or workflow:

```
your-skill-name/
├── SKILL.md       # Required, YAML frontmatter + Markdown instructions
├── scripts/       # Optional, executable code (Python, Bash, ...)
├── references/    # Optional, docs loaded only when needed
└── assets/        # Optional, templates, fonts, icons used in output
```

Skills rely on **progressive disclosure**: the frontmatter is always in context (so it decides *when* the skill loads), the SKILL.md body loads when relevant, and linked files load only on demand. Keep each level as small as it can be.

## Workflow: Creating a New Skill

### Step 1: Define 2-3 concrete use cases

Before writing anything, pin down with the user:

- What does the user want to accomplish? (outcome, not feature)
- What triggers it? Collect literal phrases users would say.
- What steps does the workflow require, in order?
- Which tools are needed (built-in, scripts, MCP servers)?
- What domain knowledge or best practices must be embedded?

Write each use case as: **Trigger → Steps → Result**. If the user is vague, propose use cases and confirm rather than guessing silently.

Identify the category, it shapes the structure:

1. **Document & asset creation**, embed style guides, templates, quality checklists.
2. **Workflow automation**, step-by-step process with validation gates.
3. **MCP enhancement**, orchestrate MCP tool calls in sequence with domain expertise.

### Step 2: Plan the folder structure

- Folder name: kebab-case only (`my-skill`, no spaces, capitals, or underscores) and it should match the frontmatter `name`.
- `SKILL.md` must be named exactly that, case-sensitive.
- Never put a `README.md` inside the skill folder.
- Keep SKILL.md under ~5,000 words; move detail to `references/` and link to it.
- For critical validations, prefer a bundled script over prose, code is deterministic, language interpretation isn't.

The rest: https://github.com/XiaomiMiMo/MiMo-Code/blob/HEAD/packages/cli/src/skill/builtin/.bundle/skill-creator/SKILL.md