Your First Custom Skill: A Personal SOP in Markdown

You ask Cowork to write the weekly status update. It comes back fine, except the headline is buried, the metrics aren't bolded the way your boss likes, and the "risks" section is missing because you forgot to ask for it. So you paste in your usual reminder: lead with the decision, bold the numbers, always include risks, keep it under 200 words.

Tomorrow you ask for a different update. You paste the same reminder again. The day after, again, slightly reworded, because you're typing it from memory each time.

The replies were never the problem. Cowork can absolutely follow your format. The problem is that how you do this lives in your head, and you re-explain it from scratch on every request.

There's a place to put a procedure once, so Cowork follows it without being told. It's a skill, and it's a fix you can build this afternoon.

#A skill is a procedure, not a fact