A skillet full of production-tested agent skills: plain SKILL.md files that turn an idea into a shipped, reviewed change. 23 skills at v0.3.0, organized as a kitchen line — find work, design it, plan it, fire it, taste it, plate it, ship it.
Skillet is a repo of reusable agent skills — "production-tested workflows for auditing, improving, and shipping repos with AI coding agents." Each skill is a plain SKILL.md (Markdown + a two-field YAML frontmatter) under skills/<name>/. It installs as a Claude Code plugin via a marketplace, but every skill is harness-agnostic: you can also copy a SKILL.md into any compatible tool or drop one into a repo’s .claude/skills/. Each skill was extracted from a real workflow that broke when done by hand.
Skillet shares Brigade’s kitchen vocabulary, applied to the build process. Each culinary name encodes when to reach for the skill.
The spine of skillet is a three-skill chain, each with a terminal handoff to the next. special finds the work; mise designs it; recipe plans it; fire builds it. Nothing skips ahead — mise will not write code, recipe will not decide design, fire will not improvise off the ticket.
The build line is the spine; the rest are the ribs — disciplines that wrap the chain and gates that guard the exit. Grouped by what they are for.
line-checkbug-huntsecurity-sweepexpeditespecialmiserecipefirepressure-testdemitasterefirereducechecksendbackstationspassplatepublish-readinessrelease-cutmemory-handoffskillifybrigade-handoffsA skill is just Markdown with a two-field frontmatter. The description is the activation trigger — it always opens with "Use when..." and usually names negative scope ("not for X") and a terminal handoff. The body opens with the metaphor and the core principle, then Steps / Rules / Common mistakes.
skills/mise/SKILL.mdmarkdown---
name: mise
description: Use before any creative or build work - to turn an idea
into a design the user approved and a written spec, before a line of
code. Pairs with pressure-test for hardening; hands off to recipe.
---
# mise
Mise en place for building: everything designed and in its place before
you cook. The deliverable is a written spec a separate session could
implement without re-deciding anything load-bearing.
## Steps
1. ...
## Rules
- No code, no scaffolding until a design is on the table and approved.
## Common mistakes
- Starting to build the thing that "looks too small to bother" designing.name / description (only two fields)No separate when-to-use field — the trigger is folded into description.description: Use when / Use before ...Doubles as the activation matcher; lists literal trigger phrases and negative scope.Mise en place for building ...House style: open with the metaphor, then the one-sentence core principle.hands off to recipeSkills declare a terminal next-step so the chain composes without guesswork.line-check, bug-hunt, and security-sweep are read-only and share one finding schema (docs/audit-report-format.md). Because every finding has the same shape and an effort estimate, the three audits merge into one leverage-sorted backlog that expedite then drains.
| Field | What it captures |
|---|---|
| [SEVERITY] title | A short imperative title prefixed by severity. |
| Station / Lens | Which audit dimension produced the finding. |
| Where | file:line, directory, or "repo-wide". |
| What | One or two concrete sentences, no hedging. |
| Why it matters | The consequence if ignored. |
| Fix | The specific action, with commands or a sketch. |
| Effort | S (<30 min) / M (<half day) / L (multi-day) — drives leverage sorting. |
The discipline skills (check, taste, refire, sendback) are the ones most likely to get skipped exactly when they matter most. They are written as hard gates with named rationalizations, so the agent cannot talk itself out of them.
Skillet is independent code, but one skill wires it to Brigade. brigade-handoffs drives the brigade-cli (operator quickstart, operator doctor, handoff draft/lint/doctor) to make agent memory boring: local drafts, linted routes, a review queue — never editing canonical memory directly. line-check is also Brigade-aware, auditing handoff/memory health when a repo uses Brigade.