---
name: create-skill
description: >
  Use this skill to create new agent skills for this project. Trigger it when the user wants to
  capture a repeatable workflow, teach the agent how to handle a recurring task pattern, or formalize
  a process that currently relies on manual instruction. Use it whenever the user says "let's create
  a skill for X", "save this workflow", or "how do I make the agent remember how to do Y".
---

# Create Skill

This skill guides you through creating a new SKILL.md for this project's `.agents/skills/` folder.

## When to trigger

- User wants to capture a workflow they've refined through conversation
- A task requires specific, repeatable steps that the agent should follow consistently
- A complex process exists in documentation but the agent keeps making mistakes
- User says "turn this into a skill" or "save this as a workflow"

## Steps

### 1. Capture intent

Ask the user:
1. What should this skill enable the agent to do?
2. When should it trigger? (what phrases or contexts?)
3. What's the expected output?

### 2. Research & define

Before writing, identify:
- What tools or MCP calls does this skill use?
- What are the common failure modes?
- Are there edge cases to cover?

### 3. Write the SKILL.md

Create `.agents/skills/<skill-name>.md` with this structure:

```markdown
---
name: skill-name
description: >
  When to trigger (be specific and a little "pushy" about when to use it).
  What it does. Include context phrases that should trigger it.
---

# Skill Title

Brief explanation of why this skill matters.

## When to trigger

- Bullet list of specific situations

## Steps

### 1. First step
### 2. Second step
...

## Example

Show a concrete before/after or user message → agent action example.
```

### 4. Keep it focused

- **Under 500 lines** — if longer, split into a main SKILL.md + `references/` files
- **Imperative tone** — tell the agent what to do, not just describe it
- **Include examples** — one concrete example is worth many abstract rules

### 5. Placement

Save the new skill to:
```
.agents/skills/<skill-name>.md
```

Inform the user so they can reload the agent context.

## Key principles

- Skills should reduce repeated instruction — if you're explaining the same thing every session, make it a skill
- A skill's `description` field is what triggers it — make it specific to when AND what
- Err on the side of making the description a little pushy; agents tend to undertrigger skills

---
*Included by [@komexa/kickoff-mcp](https://github.com/komexa/kickoff-mcp) — based on [Anthropic Skills](https://github.com/anthropics/skills)*
