From one good workflow to a reusable skill
🔁Notice repetitionThe same method, checks or structure keeps returning.
🧩Create the skillStore the stable method and describe when it applies.
🧭Cowork matches itThe description helps Cowork select the right skill.
✅Review the resultImprove the skill when the workflow—not the one task—needs fixing.
What a custom skill adds
🧭A clear use case
The description tells Cowork when to load the skill. “Creates a weekly leadership update from approved project sources” routes more reliably than “helps with reports.”
📋A repeatable procedure
The instructions can define the output sections, review sequence, evidence rules, quality standard and actions that must wait for approval.
📎Supporting material
Companion files can hold a detailed rubric, example or reference material so the core procedure remains readable.
Choose the right reusable feature
Choose
When it fits
What is reused
Normal Cowork request
The task is one-off or the method changes substantially each time.
Nothing beyond the current conversation.
Cowork Skill
Cowork should follow the same method across many different tasks.
Instructions, standards, checks and supporting files.
Scheduled task
The same work should run automatically at a time or after an event.
The task plus its timing or trigger.
Custom agent
People need a dedicated assistant with its own knowledge, role or business actions.
A broader assistant experience beyond one Cowork method.
Create and test the skill
Open CustomizeIn Cowork, open Customize, choose Skills and select Add, then Create new.
Describe the scenarioName the work, the expected inputs and the finished output.
Define the methodExplain the stable steps, checks, format and approval points.
Test real variationsTry more than one project or input set before sharing the skill.
Example: Executive Weekly Update
Create a Cowork skill called Executive Weekly Update. It should use the latest approved project information and produce a one-page update with Progress, Decisions, Risks, Next Week and Leadership Help Needed. Every red or amber risk must cite its supporting source. The skill may draft the update, but it must never send or share it without approval.
💡Key insightA skill makes a method consistent. It does not add data access, permissions or a new connection to another service.
The anatomy of a dependable skill
🏷️DescriptionExplains when Cowork should select the skill.
🧱ProcedureDefines the sequence and decisions that stay stable.
📚ReferencesHold detailed examples, rubrics and supporting material.
🛡️ControlsState evidence, approval and stop conditions.
The description is a routing rule
Cowork can select a skill from the current request. If two descriptions overlap, selection becomes unpredictable even when both instruction files are well written.
😐Too vague
“Helps with reports.” This does not identify the audience, source material, output or moment when the skill should be used.
🎯Specific enough to route
“Creates a weekly leadership status report from recent approved project updates using the five-section executive format.”
Keep only stable instructions in the skill
🧱Put the method in SKILL.md
Store the repeatable sequence, decision rules, output structure and review standard. Keep project names, dates and temporary facts in the task request.
📎Use companion files for detail
Place longer rubrics, examples or approved templates outside the main procedure. Cowork currently supports companion material within documented limits.
🛑Define what happens when blocked
Tell Cowork when to ask a question, omit an unsupported claim, stop before an action or report that required evidence is missing.
Sharing creates a maintenance responsibility
Change
What can go wrong
What to do
Procedure changes
People continue using an older shared version.
Update the source skill and re-share it.
Reference changes
An example or rubric no longer reflects the approved standard.
Replace the companion file and retest the output.
Scope expands
One skill accumulates unrelated workflows and routes poorly.
Split the method into focused skills with distinct descriptions.
Know when a skill is not enough
🔌External access needs a connection
Instructions cannot create access to another system. A plugin, connector or agent action may be required.
🤖A broader role needs an agent
Use a custom agent when users need an ongoing specialist assistant with knowledge, actions, governance or wider deployment.
⏰Timing needs automation
A skill tells Cowork how to work. A scheduled or event-driven task determines when the work runs.