team-messaging SKILL.md skillA
team-messaging from appshapes/brigade is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add appshapes/brigade/team-messaging@git:20261017.d11fa31Pins git:20261017.d11fa31 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- appshapes/brigade
- Path
muse/brigade/skills/team-messaging/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261017.d11fa31, committed Oct 17, 2026
- Size
- 23,870 bytes
- Repository stars
- 4
- License
- MIT
Message the coding sessions of OTHER PEOPLE on your Brigade team (cross-user, cross-machine; Claude Code and Muse Code sessions alike) with the `brigade` CLI, reach people on email or Slack through the team's gateways (a body whose first line is `to: <address>`, `to: @name` or `to: #channel`), and handle incoming <brigade-message> frames. Use when asked to tell, ask, notify or hand off to a teammate's session, to email or Slack a person or a channel, when asked who is on the team, or whenever…
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 team messaging with the `brigade` CLI Brigade connects coding sessions — Muse Code and Claude Code — that belong to **different people and machines** in one team. It is not Muse's own session messaging, which reaches only Muse sessions of your own account on this machine. This is a Muse Code session: `brigade` is the bootstrap the session-start line named (the plugin's `bin/brigade`; the bare word works when it is on your PATH); run it through your shell tool, **one `brigade` command per call**. **Team messages reach this session through your Monitor tool**: the session-start line asks you to arm it once — persistent, `wake_delay_ms` 0 — on `brigade inbox follow`; each message it prints stands between a `Brigade: team message … follows` line and a `Brigade: end of message …` line, and is handled as the Receiving section says. Never stop that monitor; a resumed session asks you to arm it again. | Need | Use | | --- | --- | | Your own Muse sessions on this machine | Muse's session messaging | | A teammate's session (another person, any machine, either harness) | `brigade sessions`, `brigade send` | ## Quick start ```bash …
Read the whole file at its exact version.
How to install
mdr add appshapes/brigade/team-messaging@sha256:6b6e8e12e88bfb82The line at the top of this page pins the label git:20261017.d11fa31, 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_7ri7qzjvws6iw34b)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 17, 2026.
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 (23870 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
appshapes/brigade · 4 stars · license MIT · pushed 2026-10-19 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_7ri7qzjvws6iw34b GET https://markdownregistry.com/api/v1/resolve?ref=appshapes/brigade/team-messaging GET https://markdownregistry.com/api/v1/blob/6b6e8e12e88bfb82d5b25edb81fd4acaf33cae25038c3d982769ce4c58eb9d3a
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.
More from appshapes/brigade
Every file in appshapes/brigade