Don't Build a New Skill. Borrow Someone Else's First.

You decide Cowork should turn your messy meeting notes into a clean slide deck. So you sit down and write instructions. You explain the structure you want, the tone, how to handle the title slide, what to do when a section has too many bullets. You test it, it gets one thing wrong, you add a paragraph. An hour goes by. Then another.

The deck you finally get is fine. The afternoon you spent is gone.

A week later someone shows you that a ready-made skill for building slide decks already existed (vetted, maintained, better than yours), and turning it on took thirty seconds.

The tool wasn't the problem. The reflex was: you reached for build when you should have reached for borrow. Check the shelf before you reach for the workbench.

#What a skill actually is

A skill is a packaged set of instructions Cowork loads when it's relevant: a small, named bundle that teaches it one kind of job (build a spreadsheet, format a document, run a code review) and pulls in templates or scripts if the job needs them.