How-to guide
Write your first SKILL.md
Create a working skill in ten minutes: the file layout, the header, the instructions and a first test. Includes a copy-ready template.
- Time 15 min
- Level Beginner
- Steps 6
- Updated
The best first skill is a small job you already do the same way each time: a commit message, a meeting summary, a code review.
Step by step
0/6 done-
1 Pick one job
Write down the task in one sentence and collect two real examples of it. If you cannot describe it in one sentence, it is probably two skills.
-
2 Make the folder and file
Create a folder with a lowercase, hyphenated name and add a file called
SKILL.mdinside it.commit-message-writer/ SKILL.md -
3 Write the header
The header sits between two lines of three dashes. It needs a
name(the same as the folder) and adescription.--- name: commit-message-writer description: "Writes a clear commit message from staged changes. Use when asked to commit or to write a commit message." ---Put the description in quotes if it contains a colon.
-
4 Write the instructions
Under the header, write what the AI should do, in plain language: the steps, the rules, and the exact shape of the answer.
# Commit message writer ## How to work 1. Look at the staged diff and recent commit messages. 2. Write a subject line of 50-72 characters, imperative mood. 3. Add a body only when the reason is not obvious. ## Rules - One logical change per commit. - No filler such as "various fixes". ## Output The message in a code block. -
5 Install it and try it
Put the folder in your skills folder (see How to install a skill), restart your tool, and ask: "Write a commit message for what I have staged." Watch whether the skill loads and whether the result follows your rules.
-
6 Improve it
When the result is wrong, change the instructions, not the request. Add the rule that was missing, or an example of what you wanted. Share it on Promptsio when you are happy with it.
Was this helpful?
Thanks — that helps us improve this page.