Package a repeatable team SKILL.md for Claude Code
Claude Code turns a workflow your team already runs into a portable SKILL.md with triggers, guardrails, and a done checklist.
One skill file in the repo that any teammate can invoke the same way, with scope written tight enough that drift shows up in review.
- 1
Paste a real run, not the ideal
Include the last mistake someone made and how you caught it. That becomes the pitfalls section.
- 2
Commit under .claude/skills or your team path
Put the file where your repo already documents agent rules. Link it from CONTRIBUTING or the README in one line.
- 3
Dry-run on a second machine
A teammate invokes the skill on a fresh clone. If they improvise steps, tighten the checklist before you call it team standard.
The prompt to paste
Turn this team workflow into a Claude Code skill as a single SKILL.md file. Workflow we already run: [paste: when we do it, who owns it, inputs, outputs, and the last time someone did it wrong] Repository context: [monorepo or single app, languages, folders agents should not touch] Write SKILL.md with these sections, in order: 1. Title and one-sentence purpose (what job this skill does, not tool marketing). 2. When to use / when not to use (three bullets each, concrete). 3. Required inputs the human must provide before the agent starts. 4. Steps the agent should follow, numbered, each ending with a verifiable check. 5. Example prompts (two): one minimal, one with realistic messy input. 6. Pitfalls: five mistakes that cause bad merges or wrong files, and how to catch them in review. 7. Done means: a checklist the human can tick without reading the whole diff. Rules: - Do not invent commands, env vars, or CI jobs that are not in the workflow paste. - Prefer paths relative to repo root. If a path is unknown, write [confirm path] instead of guessing. - Keep the skill focused on one job. If the paste describes two jobs, pick the primary one and list the other under when not to use. - Output only the SKILL.md body in markdown. No preamble.
A skill that says “use best judgment” will diverge by laptop. Every step needs a check a reviewer can see in the diff or the command output.
Sample case written by Hidden Logic Lab. Not affiliated with Claude Code.
More in Coding
Get new cases in your inbox
Weekly notes on new use cases and agent workflows. No product pitches.