AI Skill Files Explained: What SKILL.md Is and How to Write One
An AI skill file is a reusable instruction document that makes a model do one job your way, every time. Here is what goes inside SKILL.md and how to write your first one.
An AI skill file is a short, plain text document that tells an AI model how to do one specific job the way your business wants it done. SKILL.md is the usual name for that file: a markdown document holding the role, the steps, the rules and the output format for a single task. You write it once, save it, and reuse it every time the job comes up, so the result stops depending on who typed the prompt that day.
Why a skill file beats a one-off prompt
Most teams start with AI the same way. Someone types a request, gets a decent answer, then types a slightly different request the next day and gets a slightly different answer. The knowledge of what works stays in one person's head, or in a chat history nobody can find.
A skill file fixes that. It turns a good prompt into a small company asset, like a template or a checklist. Anyone on the team can load it, and the model follows the same instructions each time. When you learn something new, you edit the file once and everyone benefits.
- Consistency: the same tone, structure and rules on every run.
- Speed: nobody rewrites the background and the rules for each request.
- Handover: a new hire can produce work at the house standard from the first week.
- Control: your red lines, such as what never to promise a customer, are written down.
What goes inside SKILL.md
A skill file is ordinary text under a few headings. There is no code in it. A useful file answers six questions for the model.
1. What the skill is and when to use it. Start with a name and a one or two line description. Tools such as Claude read that description to decide when the skill applies, so write it plainly: what the skill produces and the situations that should trigger it.
2. Who the model is acting as. Give it a role that matches the job, for example a senior accounts assistant at a trading company in Dubai who writes polite, firm payment reminders.
3. What it needs from you. List the inputs: the customer name, the invoice amount, the due date, the language of the reply. Tell the model to ask for anything missing instead of guessing.
4. The steps to follow. Describe the work in order, the way you would brief a capable new colleague. Keep each step to one action.
5. The rules. Write down what must always or never happen. Use AED for amounts. Never invent a figure. Keep replies under 150 words. Pass anything that looks like a dispute to a manager.
6. What the output looks like. Describe the format: a subject line then three short paragraphs, or a bullet summary followed by next steps. If you have a strong example of a finished piece, paste it in and label it as an example.
How to write your first one
Pick one task your team repeats every week and where people already agree on what good looks like. Quotation follow-ups, meeting summaries, supplier comparison notes and job advert drafts are all good starting points.
Open a blank document and explain the task as if you were briefing a smart person who has never worked in your company. Where a rule is not obvious, say why it exists. Models follow instructions better when they understand the reason, the same way people do.
Then test it. Run the file on three real cases from last month, including one awkward one. Read the output next to what your best person actually sent. Every gap you see is a missing instruction, so add a line to the file and run it again. A few rounds of this is normally what it takes before a team trusts a file.
If you would rather start from a structure than a blank page, the skill file builder in Labs asks you the questions above and assembles the file for you. The Vault holds ready made skill files you can copy and adapt, with a new one added every day.
Using the same file in Claude, ChatGPT, Gemini and Kimi
A skill file is just text, so it travels. In Claude you can install it as a skill or paste it into a project's instructions. In ChatGPT you can place it in a custom GPT or a project. In Gemini it fits inside a Gem. In Kimi, or any other assistant, you can paste the file at the top of a conversation and then give it the inputs.
Common mistakes
- Covering five jobs in one file. One skill, one job. Split the rest into their own files.
- Vague quality words. Professional and engaging mean little. Describe the reader and the result you want.
- No example. One real example teaches more than ten adjectives.
- Client data inside the file. The file holds instructions, not customer records. Add data at run time and follow your company's data rules.
Questions people ask
Do I need to be technical to write a skill file?
No. If you can write a clear brief for a new employee, you can write a skill file. It is plain language under a few headings, saved as a text or markdown document.
How long should a skill file be?
Long enough to remove guesswork and no longer. Many useful files fit on one page. If yours runs past two or three pages, it is probably covering more than one job and should be split.
Is a skill file the same as a prompt?
A skill file is a prompt that has been written down properly, tested and saved for reuse. The difference is discipline: it has a defined job, inputs, rules and an output format, and the whole team uses the same version.
AI Invoice Processing in the UAE: A Seven-Step Playbook for Supplier Bills
AI invoice processing means a model reads each supplier invoice, extracts the fields your team types by hand, checks TRN, VAT and duplicates, and sends a draft to a person for approval. This playbook takes a UAE business from counting invoices to a live pilot in seven steps.
AI Readiness Checklist: Ten Things to Have in Place Before Your First Automation
A business is ready for its first AI automation when it has one clear task, a named owner, written answers, tidy data, company accounts, basic rules and a way to measure the result. Use these ten checks before you spend anything.
Client Data Safety With AI Tools: Rules for Your Team
A practical set of rules for using AI assistants without exposing client information: what never to paste, which accounts to use, and who checks what.
The daily skill, in your inbox
One email each morning with the new drop. Unsubscribe in one click.
