Skills Aren't Features. They're Specialized Brains You Switch On.

You spend twenty minutes writing a skill that captures how your team formats client proposals: the headings, the tone, the boilerplate you paste into every one. You save it, feel clever, and move on.

A week later you ask Cowork to draft a proposal for a new account. It writes something competent and generic. None of your formatting. None of your boilerplate. The skill you built sits there, unused, like a tool still in its packaging.

You assume the skill is broken, or that skills are just hype.

The skill isn't broken. You never told Cowork when to reach for it.

#What a skill actually is

A skill is not a button or a feature you toggle. It's a small folder of instructions (at minimum a file called SKILL.md) that packages a specialized way of working: a workflow, a set of conventions, the steps an expert would follow. Think of it as an onboarding guide you'd hand a new specialist on your team.