Writing a good SKILL.md file by hand is a small skill in itself — knowing what to include, how narrow to scope it, what instructions actually change model behaviour. Ask Mio removes that barrier with two related features from the “How Mio works” list: Skill creator, which builds a custom expert from a conversation rather than a hand-written file, and Automatic skill, which picks the closest matching skill for you when you haven’t chosen one. This guide, following on from the SKILL.md format explainer earlier in this series, covers both.
Skill creator: building an expert without writing the file yourself
The features page describes it plainly: “Create your own expert: name it, describe when to use it and what it must do. It appears in your Skills list and can be exported as SKILL.md.” The process is conversational rather than a form with technical fields — you tell Mio what you want the expert to be, when it should be used, and what rules or standards it must follow, and Mio turns that description into a structured SKILL.md file behind the scenes. It then shows up in your Skills list exactly like any pre-built or imported skill, ready to select for a conversation.
The export option matters for the same reason the open format matters generally: a skill you built inside Ask Mio isn’t stuck there. Because it’s exported as a standard SKILL.md file, you can keep a copy, share it with a colleague, or load it into another SKILL.md-compatible tool if you use more than one.
What makes a good skill creator brief
The three inputs the features page names — name, when to use it, what it must do — map directly to what actually determines quality. The name should be specific enough to disambiguate from your other skills (“EU VAT Invoice Checker,” not “Finance Helper”). The “when to use it” description is what powers Automatic skill’s matching, so it should describe the actual trigger conditions clearly — the kind of question or task that should activate this skill, not a vague statement of the general topic area. And “what it must do” is where the real instructions live: format requirements, tone, facts or rules it must apply consistently, and anything it must never do (a support skill that must never promise a refund without escalation, for instance). Vague input in any of these three produces a vague skill; specific input produces one that behaves consistently.
A worked example
Building a skill for reviewing supplier contracts against your company’s standard terms might look like: name it “Supplier Contract Reviewer”; “use this when I paste or attach a supplier or vendor contract and ask for a review”; “check for payment terms longer than 45 days, flag any exclusivity clause, confirm a termination-for-convenience clause exists, and always note whether liability is capped — never approve a contract outright, only flag issues for a human decision.” That description, given in plain conversation, becomes a SKILL.md file that consistently applies those specific checks every time the skill is loaded, instead of you re-explaining the same standard in every new contract review conversation.
Automatic skill: picking the closest one and saying which
The companion feature solves a different problem: once you have several skills, remembering to manually select the right one before every relevant question is its own friction. Automatic skill removes that step — the features page describes it as: “When a chat has no skill chosen, Mio picks the closest one for the question (and says which) instead of answering as a generalist.” Ask a question that clearly matches your Supplier Contract Reviewer skill, and Mio loads it automatically and tells you it did, rather than answering as a generic assistant and leaving you to notice the mismatch yourself.
The “and says which” part is the detail that makes this trustworthy rather than opaque — you always know whether a specific skill shaped the answer or whether Mio answered generically, which matters if you’re relying on a skill’s specific rules being applied. If it picked the wrong one, or none applied when one should have, you can correct it in the same message rather than discovering the mismatch later.
What changes when automatic matching is on
| No skill selected, Automatic skill off | Automatic skill on | Skill manually selected | |
|---|---|---|---|
| Default behaviour | Answers as a generalist | Matches the closest skill automatically | Uses the selected skill for the whole chat |
| Tells you which skill applied | N/A — no skill used | Yes, every time it loads one | You already know, since you picked it |
| Risk of a mismatch | None — always generalist | Low, and visible when it happens | None, but you must remember to select it |
| Best for | One-off, unrelated questions | Regular use across several specialised skills | A single, focused work session |
Building a small library of skills over time
The two features compound. Skill creator lowers the cost of making a new skill enough that it’s worth doing for narrower and narrower use cases — a skill for one recurring report format, a skill for one client’s specific communication style, a skill for one compliance checklist — rather than reserving skill-building for only the biggest, most general needs. Automatic skill then makes having several of these genuinely convenient rather than a maintenance burden, since you’re not manually switching between them for every question. Together, they turn “write a custom AI assistant” from a technical project into something closer to writing down a process you already know, once, and having it consistently applied afterward. A small team might end up with a handful of narrow skills covering their most repeated tasks — a report format, a client’s tone of voice, a compliance checklist — each one used often enough to be worth the few minutes it took to describe, and none of them requiring anyone on the team to know what a SKILL.md file even looks like under the hood.
Common mistakes when building a skill this way
The most frequent one is scoping a skill too broadly out of a wish to make it maximally useful — a skill meant to cover “all of marketing” ends up with instructions so general they barely change Mio’s behaviour compared to answering without any skill at all. The fix is almost always to split one broad idea into several narrow skills: a campaign brief skill, a social copy skill, a competitor analysis skill, each with its own tight “when to use it” description, rather than one catch-all that has to cover too much ground to be genuinely specific about any of it.
The second is leaving out the negative instructions — what the skill must never do — and only specifying what it should do. For anything with real consequences (a support skill, a compliance-adjacent skill, a financial one), explicit boundaries matter as much as the positive instructions: “never commit to a delivery date without checking the calendar first” is often the single most useful line in a skill, because it’s the mistake a generalist answer is most likely to make by trying to be maximally helpful in the moment.
The third is writing the “when to use it” description around a topic rather than a trigger. “About customer support” is a topic; “when I paste a customer complaint and ask how to respond” is a trigger, and triggers are what Automatic skill actually matches against. A skill described by topic alone tends to either over-trigger (loading for anything vaguely related) or under-trigger (missing genuinely relevant questions phrased differently than expected).
Iterating on a skill after real use
A skill’s first version is a hypothesis about what instructions will produce consistently good output — it’s rarely perfect on the first try, the same way a first draft of a style guide for a human team usually needs a revision or two once people actually try following it. After using a skill for a week or two, revisit it with what you’ve noticed: a rule it forgot to apply, an edge case it handled inconsistently, a tone adjustment that would make the output more useful. Because updating a skill is the same conversational process as creating one, this revision loop stays cheap enough to actually do, rather than something that only happens once and then goes stale.
Where this fits
Skill creator and Automatic skill are 2 of the 9 features under “How Mio works”, both built on the SKILL.md format covered in the previous guide. The final article in this batch covers Headroom, document memory and the privacy tools — the remaining account-level features in this section. Every guide here sits under the “What Mio can do” tag.
Skills versus the pre-built experts
It’s worth distinguishing a custom skill from Ask Mio’s 39 pre-built experts covered elsewhere in this series — the experts are ready-made personas (Legal assistant, Accountant, Copywriter and so on) you can turn Mio into immediately, with no setup. A custom skill is for the specific, narrower thing none of those 39 pre-built experts quite covers: your own company’s exact process, a specific client’s tone, a checklist unique to your team. Use a pre-built expert when a general professional persona is close enough; build a custom skill when the general version doesn’t capture something specific you need repeated exactly the same way every time. Many people end up using both — a pre-built expert for general work in that domain, and one or two narrow custom skills layered on top for the handful of tasks that need exact, repeatable rules.
Frequently Asked Questions
Do I need to know Markdown or any technical format to use Skill creator?
No — the process is a plain-language conversation; Mio builds the SKILL.md file from what you describe, so no direct file editing is required to create a working skill.
Can I edit a skill after creating it?
Yes — return to it and describe what should change, the same conversational process used to create it in the first place, rather than editing the underlying file by hand (though you can, since it’s exported as standard Markdown). There’s no limit on how often you revise it, and the cost of doing so is a short conversation rather than a rebuild.
What happens if Automatic skill picks the wrong one?
Because it always tells you which skill it loaded, a wrong match is visible immediately — correct it in the same message by naming the skill you actually wanted, or by turning off automatic matching for that conversation and selecting manually.
Can a skill I create be exported and used outside Ask Mio?
Yes — Skill creator exports as a standard SKILL.md file, which is the same open format used by other compatible AI assistants, so the file itself isn’t locked to Ask Mio.
How many skills can I have?
There’s no specific number stated on the features page; practically, the more skills you have, the more Automatic skill’s matching does real work distinguishing between them, which is where a clear “when to use it” description for each one matters most.
Does Automatic skill slow down responses while it decides?
The matching happens as part of processing your question rather than as a separate, noticeably slow step — it’s designed to be a normal part of how a conversation starts, not an extra wait.
Is Skill creator available on every plan?
Bigger account-level features under “How Mio works” vary by plan — check the pricing page for what’s included at each tier.
The Bottom Line
Skill creator turns building a custom AI expert into a conversation instead of a technical project, and Automatic skill makes having several of them genuinely practical by loading the right one and telling you it did. Together they make the open SKILL.md format from the previous guide something you’d actually use regularly, not just a technical detail. Try building your first skill on the Chat plan, starting narrow and revising once you’ve seen it handle a few real questions.