Skills and Skill Guard
Fix skills that won't import, won't switch on, get flagged or blocked by Skill Guard, or that a bot ignores.
A skill won't import
- Check the file. A skill is a
SKILL.mdfile with frontmatter between two---lines at the top. It needs anameand adescription. - Check the name. Lowercase letters and numbers with single hyphens, up to 64 characters, such as
weekly-report. In a folder or zip, the folder name must match thenameexactly. - Check the size. A
SKILL.mdcan be up to 256 KB. The description can be up to 1,024 characters. - Check the link. A GitHub link must point to a skill, not a whole repository of unrelated files.
Files are missing after import
Murage uses the SKILL.md file only. Scripts, reference files and other files in the folder are skipped, and the review lists what was left out. Move anything the bot needs into SKILL.md.
I imported a skill but the bot doesn't have it
Imported skills land switched off, for every bot. Open Bot settings → Skills on the bot, choose Add a skill, pick it, and choose Enable.
"Needs a look"
Skill Guard found something that deserves a read. Open the skill and read the findings: each one says what matched, quotes the text and names the file. If you understand it and it's fine, for example a skill that's meant to explain what a password manager does, choose Use it anyway. If you don't understand it, don't switch it on.
"Blocked"
A blocked skill can't be switched on. Skill Guard blocks a skill for a critical finding, such as reading passwords or sending data to an outside site, or a serious finding from Murage's own rules. If it's your own skill:
- Read the finding and the quoted text.
- Rewrite that part. For example, remove a pasted key, a command that uploads files, or a line telling the bot to ignore its instructions.
- Save. The skill is scanned again when you edit it.
There's no override for Blocked.
A skill that was on is now off
Skill Guard scans every skill again each time Murage starts, and after every edit. If a scan now blocks it, it's switched off. This can happen after an update adds new checks. Open the skill to see why.
The bot ignores a skill
- Check it's enabled for that bot, not just imported.
- Check the description. Bots see a short index of their skills (name and description) and open a skill when the description matches the job. A vague description, such as "Useful stuff", rarely gets opened. Say what it does and the words people use to ask for it.
- Check how many skills the bot has. The index fits about 15 skills. A bot with many skills may not see all of them in the index. Keep each bot's skills to its job.
- Ask for it by name to test: "Use the weekly-report skill."
- Check the engine. Some engines follow skills better than others.
/learn doesn't do anything
- Switch it on first: Settings → Experimental → Teach a skill.
- The bot's engine must support it.
- The skill lands switched off. Look for the card asking you to Enable it.
A library skill was flagged
Most library skills are clean, and a small number are marked Needs a look. Read the finding before you choose Use it anyway, the same as for any other skill.
See also: Writing your own skills and Skills, Skill Guard and /learn.