brigade-work SKILL.md skillA
brigade-work from escoffier-labs/brigade is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add escoffier-labs/brigade/brigade-work@git:20260726.5cf4828Pins git:20260726.5cf4828 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- escoffier-labs/brigade
- Path
src/brigade/templates/skills/brigade-work/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260726.5cf4828, committed Jul 26, 2026
- First version recorded
- Jun 29, 2026
- Size
- 7,094 bytes
- Repository stars
- 78
- License
- MIT
Use at the start of any work session and whenever you verify a change in a Brigade-wired repo or workspace - routes work through Brigade so verification, outcomes, evidence export, and handoffs are captured (verify with capture → outcome from run → evidence brief next time) instead of leaving Brigade installed-but-dormant. Triggers on starting a task, running tests/checks, or finishing a session.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# brigade-work Brigade only earns its keep if real work flows through it. Installed and never used, it is dead weight: the daily brief is empty, the outcome ledger never fills, and `outcome rank` says "ranking: none". This skill is the loop that feeds it. Check what is pending, run your verification *through* Brigade so it produces a signed receipt, record the outcome against the skill or card that did the work, export receipts so the next run gets an evidence brief, and hand off what you learned. **Core principle:** the model never grades its own work. A real exit code captured as a Brigade verify or run receipt is the only signal that counts. Route verification through Brigade, capture the outcome, feed receipts forward via MiseLedger when installed, and the loop is honest and measured (`context_eval.brief_hit_rate`). ## When this applies The repo or workspace is Brigade-wired: a `.brigade/` directory exists, or `brigade status --target .` succeeds. If neither is true, this skill does not apply (run `brigade init` first only if the user wants Brigade here). ## The loop ### 1. Start: see what is pending At the start of a work session, before deciding what to do: ```bash …
Read the whole file at its exact version.
How to install
mdr add escoffier-labs/brigade/brigade-work@sha256:822ce10efce89c14The line at the top of this page pins the label git:20260726.5cf4828, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2lunjwistoyqnpjn)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 29, 2026 and Jul 26, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260726.5cf4828 latest | 2026-07-26 | 5cf4828 | 7,094 B | A | view · diff |
| git:20260709.08e43b7 | 2026-07-09 | 08e43b7 | 6,902 B | A | view · diff |
| git:20260629.d0de3de | 2026-06-29 | d0de3de | 5,191 B | A | view · diff |
| git:20260629.0bf9e0e | 2026-06-29 | 0bf9e0e | 4,131 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7094 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
escoffier-labs/brigade · 78 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2lunjwistoyqnpjn GET https://markdownregistry.com/api/v1/resolve?ref=escoffier-labs/brigade/brigade-work GET https://markdownregistry.com/api/v1/blob/822ce10efce89c14964cacba6627728104f167bae0f065465bf5ff49af018261
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.