Generate a valid SKILL.md from a workflow you already repeat
Fill in what the skill does and when it should be used, and this builds a SKILL.md that passes the specification's rules. The description is composed for you in the shape the spec asks for, because a missing when clause is the most common reason a finished skill never loads. Everything runs in your browser.
Lowercase letters, numbers and hyphens. The folder must have this exact name.One sentence, in the words a colleague would use.The situations and words that should trigger it. This half decides whether it ever loads.One per line. Procedure, not background.What the finished result looks like. This is what stops format drift.
Nothing is uploaded. The file is generated in your browser.
Your skill
Not valid yet: check the name and description
Composed description
...0 / 1024
SKILL.md
---
name: skill-name
description:
---
# skill-name
## Steps
1. Describe the first step here.
## Output
Describe the shape of the finished result here.
Folder
skill-name/
└── SKILL.md
Why it asks for two sentences instead of one box
An empty description box produces a description about what the skill does, which is the half that agents match on least. Splitting the question forces both halves to exist: the action, and the situation that should trigger it. The generated line is the one you would have had to learn to write anyway.
What it does not do
It writes a valid, well shaped starting point. It does not know your subject matter, so the steps it emits are the steps you typed. The name is normalised to the characters the spec allows, and the folder must be renamed to match it. Read the result before you commit it, the same as any generated file.