Write a Cursor skill

How to name, describe, and structure a skill so Cursor picks it up for the right jobs and ignores it otherwise.

Loaded on demand when the task matches the description.

Install path

.cursor/skills/write-cursor-skill/SKILL.md

---
name: write-cursor-skill
description: Draft or revise a Cursor skill (SKILL.md) with a sharp description, clear trigger, and a short procedure. Use when the user wants a reusable agent workflow.
---

# Write a Cursor skill

## Skill vs rule vs prompt

- **Rule** — short, always or often in context. Coding standards, voice, stack constraints.
- **Skill** — a procedure with steps, loaded when the description matches the task.
- **Prompt** — a one-off you paste. Promote it to a skill when you reuse it.

## Description (the trigger)

The YAML `description` is how the agent decides to open the file. It must include:

- What the skill does
- When to use it (verbs and situations)

Bad: “Helps with frontend.”
Good: “Audit a UI for generic AI aesthetics and rewrite the worst screens. Use when the user asks to polish or remove slop.”

## Body

Keep the body a procedure:

1. Inputs you need
2. Steps in order
3. Guardrails (what not to do)
4. What “done” looks like

Do not paste a whole style guide into a skill. Link to a rule for standing constraints.

## Files

Save to `.cursor/skills/<kebab-name>/SKILL.md`. Optional: `reference.md` for details the agent should read only after it decides the skill applies.