Write a skill that actually runs
write-a-skill
A skill needs a trigger, an input, an output, and a stop. Without a stop, it keeps guessing.
for Grok Bot · unofficial, not affiliated with xAI
CNPS0.1.02026-11-18New
Paste this note into Grok Bot and say: follow this note.
Note: Write a skill that actually runs
A skill needs a trigger, an input, an output, and a stop. Without a stop, it keeps guessing.
For: People writing their own skill, or editing one from this registry.
What to check:
1. Gives a skeleton you can finish, not style advice.
2. Replaces “do a good job” with an output you can open.
3. Requires you to name the actions that are not allowed, including send and delete.
Steps:
1. Create a file from the skeleton. Use the same hyphenated name in the file and in name.
2. Write description as what it does, not as a tagline.
3. Name a path for the output. A result with no path is missing on the next run.
4. Pass it through Skill check, then run one example you already know the answer to, using Test once before you trust it.
---
name: your-skill-name
description: One sentence on what it reads and where it writes.
---
Trigger: use when the user asks for ...
Input: require .... If it is missing, stop and ask. Do not invent it.
Steps:
1. Read ...
2. Write only from the input and from tool results.
3. Write the result to outputs/name.md.
Stop: stop when that file is written. Do not send, do not delete other files, do not change account settings.
Failure: if you cannot finish, end the file with "incomplete" and the missing piece.
Do not:
- Do not write “decide for yourself whether to send.”
- Do not let this skeleton grant sending, deleting, or paying.
- Do not expect this registry to install the snippet into an account.
Paste this note into Grok Bot and say: follow this note.What it does
- Gives a skeleton you can finish, not style advice.
- Replaces “do a good job” with an output you can open.
- Requires you to name the actions that are not allowed, including send and delete.
Who it is for
People writing their own skill, or editing one from this registry.
How to put it in Grok Bot
- Create a file from the skeleton. Use the same hyphenated name in the file and in name.
- Write description as what it does, not as a tagline.
- Name a path for the output. A result with no path is missing on the next run.
- Pass it through Skill check, then run one example you already know the answer to, using Test once before you trust it.
Example
SKILL.md skeleton
---
name: your-skill-name
description: One sentence on what it reads and where it writes.
---
Trigger: use when the user asks for ...
Input: require .... If it is missing, stop and ask. Do not invent it.
Steps:
1. Read ...
2. Write only from the input and from tool results.
3. Write the result to outputs/name.md.
Stop: stop when that file is written. Do not send, do not delete other files, do not change account settings.
Failure: if you cannot finish, end the file with "incomplete" and the missing piece.Connectors it needs
No connector.
Safety and permissions
- Do not write “decide for yourself whether to send.”
- Do not let this skeleton grant sending, deleting, or paying.
- Do not expect this registry to install the snippet into an account.
Risk: Low
Questions
Is a longer prompt more reliable?
No. Length without an output path and a stop line still ends in the chat, or in an action you did not name.
Do I write both languages in one file?
Set the working language in the output rule: use the language the user used. Keep the field names stable so you can search them later.
0.1.0
2026-11-18
First published text. A skeleton, not an installer.