One Skill Per Workflow, Not Per Topic

You decide to get serious about skills. Marketing is a big part of your week, so you build a skill called marketing and pour everything in: your email cadence, the way you name campaigns, your tone rules, the brief format for the agency.

A week later you ask Cowork to draft a launch email. It writes something competent and bland: none of your cadence, none of your naming. Another day you ask it to summarize last quarter's spend and it tries to apply your tone rules to a spreadsheet.

You assume the skill is too thin, so you add more. It gets worse.

The skill isn't underfed. You built it around a topic instead of a job, and a topic is something Cowork can't actually do.

#A topic is a category; a workflow is a job

"Marketing" is a heading on an org chart, a category holding a dozen unrelated jobs, from writing emails to reading reports, that share almost nothing about how they're done.