Claude Cowork Skills Guide: Build Your Own Team Workflows

The Philosophy: Small Inputs, Big Outputs

The fastest, most reliable Claude Cowork "skill" is a well-written system prompt saved to your workspace. It acts like a persistent instruction set for every conversation in that project — Claude already knows what role to play, what format to use, and what it should never do.

The second-best option is a reusable prompt template saved as a workspace artifact that any team member can open and fill in. Unlike external plugins, these are fully transparent, editable by your team, and require no third-party trust.

Step-by-Step: Build a Reusable Team Workflow

1. Describe the task precisely. What are the inputs your team provides each time? What should the output look like — a table, a list, a document? What should Claude never do in this workflow?
2. Paste the prompt template below into your Claude Cowork workspace.
3. Review the output before saving. Ask Claude to explain each step. If anything is unclear, ask for a simpler version.
4. Save to a shared artifact — any team member can open it, fill in their specific inputs, and run it. The artifact persists for 90 days (as of the March 2026 update).
5. Add a workspace system prompt for workflows that should run automatically on every conversation in a project. Settings → System Prompt → paste your instruction.

Copy This Prompt

Paste into Claude Cowork to generate a reusable team workflow — fill in the bracketed sections:

"Build me a reusable Claude workflow for [describe the task clearly].

Inputs my team will provide each time they use this:
[List the specific inputs — e.g. 'raw meeting notes', 'a code diff', 'customer feedback text']

Output format: [table / bullet list / structured document / JSON]

Constraints:
- Claude must never [list anything off-limits — e.g. 'make assumptions about decisions not in the notes']
- Keep the output under [word or line limit if relevant]

After generating the workflow output, also give me:
1. A system prompt version I can paste into workspace settings so this
   behaviour is always active for this project
2. A one-paragraph description of the workflow I can use as artifact title"

Ready-to-Use Workflow Templates

Meeting Notes → Action Items

"Take these raw meeting notes and extract:
1. Decisions made (numbered list)
2. Action items — each with: owner name, task description, deadline (or 'TBD')
3. Open questions that need a follow-up

Format as a structured document with three sections.
Do not infer owners or deadlines that aren't explicitly stated in the notes.
Flag any ambiguous items with [NEEDS CLARIFICATION].

Meeting notes:
[paste your meeting notes here]"

Code Review Assistant

"Review the following code diff for:
- Bugs or logic errors
- Security issues (injection, credential exposure, unsafe input handling)
- Performance concerns
- Style and readability issues

For each issue found:
- Line number(s)
- Issue type (Bug / Security / Performance / Style)
- Severity: Low / Medium / High / Critical
- A suggested fix (code snippet where applicable)

If no issues in a category, say 'None found.'

Code diff:
[paste diff here]"

Customer Feedback Triage

"Read the customer feedback items below and for each one:
- Category: Bug Report / Feature Request / Billing / General Question / Praise
- One-sentence summary suitable for a product backlog (for Bug and Feature only)
- Priority signal: High / Medium / Low based on language urgency

Return as a table with columns: # | Category | Summary | Priority

Feedback items:
[paste feedback here]"

Weekly Team Summary

"Summarise this week's work from the notes below into three sections:
1. Key decisions made (bullet list, max 5)
2. Work in progress (what's actively being worked on, by whom if mentioned)
3. Blockers (anything explicitly called out as blocked or waiting)

Keep each section to max 5 bullets. Use plain language — no jargon.
Do not include anything not mentioned in the source material.

Source material:
[paste this week's notes, messages, or artifact content here]"

Document Simplifier

"Rewrite the following document for a non-technical reader.
Requirements:
- Replace all technical terms with plain-English equivalents (or explain them in parentheses on first use)
- Maximum 8th-grade reading level
- Preserve all key facts — do not omit or change meaning
- Keep the same structure (headings, sections) as the original

Source document:
[paste document here]"

Turning a Workflow into a Workspace System Prompt

If you want Claude to behave a certain way for every conversation in a project — without any team member needing to paste a prompt — add it as the workspace system prompt:

1. In your Claude Cowork workspace, go to Settings → System Prompt.
2. Paste an instruction like: "You are a code review assistant for the [Team Name] engineering team. For every code diff shared with you, automatically apply the code review format: bugs, security, performance, style — each with severity and suggested fix."
3. Save. Every conversation in this project now starts with that instruction active.

System prompts are the closest equivalent to an installed "skill" in Claude Cowork — they're persistent, team-wide, and completely transparent.