The second time you do the client report with a bot, you type the same eleven steps you typed the first time. Open the notes folder, list what shipped, keep it under 250 words, don't promise dates, save it as a draft. The bot did it well last week. It has no idea it did it last week, unless you tell it to keep the steps.
Sean Donahoe, our founder, on a coaching call in October: "Once you've done this once, tell it to turn it into a skill. It will take the entire process, everything you've done step by step, and then turn it into a skill."
In Murage that's /learn.
What a skill is
A skill is a written procedure a bot follows: a folder with a file called SKILL.md, a name, a description of when to use it, and the steps in plain words. It doesn't connect an app or add a tool. It tells the bot how to use what it already has. Murage ships with a library of 2,237 of them under Settings > Skills, and the ones you teach sit next to those under Your skills.
Teaching one
It's on by default; the Teach a skill switch is at the top of Settings > Skills. In a chat with a bot whose engine supports it, right after you've done the job together:
/learn how we just wrote this week's client report
You can point it at "what we just did", at a description, a folder or a web address. The bot writes the skill, and a card asks you to Enable it. Until you do, nothing uses it. It shows as Learned in chat in the bot's skills, and you can open it in the editor and read every line before it goes live. Read it. How good a learned skill is depends on the bot's engine, and the point of the file being plain text is that you fix the one step it got wrong rather than teaching the whole thing again.
The description line matters more than the steps. A bot doesn't read every skill on every turn. It sees a short index, one line per skill, up to 15 of them, and opens the full skill when the description matches the job. So a learned skill whose description says "Friday client report, status email, weekly update" gets picked up when you ask for any of those, and one whose description says "report" gets picked up for everything.
Skill Guard checks it as well, the way it checks every skill when it's imported, switched on or edited, and again each time Murage starts. Clean means ready. Needs a look means it only switches on after you choose Use it anyway. Blocked means it can't be switched on at all.
Which jobs to teach first
The ones you've done with a bot three times and corrected the same way each time. The client report. How you qualify a lead. The way you answer a refund request. Each has checks and exceptions in it by now. The SOP writer use case is the same thing from the other direction: you walk your Chief of Staff through a job, it asks what you skipped, and it writes the procedure as a skill with the steps, the checks and the exceptions.
Don't teach a job you've only done once. On the first run you haven't hit the exceptions yet, so the skill won't have them.
There's a second way in, from memory. A bot that has picked up a way of working over several conversations shows it as a memory record, and Review as skill on that record asks a bot to turn it into a skill, which you still approve.
Once it's on, a routine can run the skill on a schedule, so the Friday report becomes a routine that drafts the update for you to send. Any bot can use it, so the report doesn't depend on the one bot that learned it. And it goes in the export when you share a team with your staff, so the person who takes over client reports gets the procedure. Nobody has to write them a message about how you used to do it.
The skill is yours to edit, duplicate or switch off in Settings > Skills. If you'd rather write one from scratch, writing your own skills has the format and a worked example. Otherwise download Murage, do the next repeating job with a bot, and when it comes out right, type /learn.