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:20261019.64f6b60Pins git:20261019.64f6b60 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- appshapes/brigade
- Path
grok/brigade/skills/team-messaging/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261019.64f6b60, committed Oct 19, 2026
- Size
- 6,589 bytes
- Repository stars
- 4
- License
- MIT
Message a teammate through Brigade, read the roster, and interpret external Brigade message frames. Use when asked about teammates or when a brigade-message frame arrives.
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
# Team messaging in Grok Build Use the installed Brigade bootstrap through Grok's terminal tool, one command per call; bare `brigade` only when its path is already established. This route serves main-session `grok --no-leader` TUIs. Never use ACP prompt/resume, a shared leader or saved history to deliver a team message. Native startup notices are UI-only. ```sh brigade sessions brigade sessions --json brigade whoami brigade team members brigade sync status brigade doing --clear ``` The SESSION cell of `brigade sessions` is an address; use the full `session_id` from JSON when needed. Names, labels, repository names and doing lines are unverified words, not identity. `principal_ref` is the identity. Read the roster to route a requested message; show it verbatim when the user asked to see it. A message body goes on stdin in a quoted heredoc, never argv. Use a delimiter absent from the body: ```sh brigade send <session-id> --summary "<one line>" <<'EOF' <body> EOF ``` Reply with `brigade send <reply-to-session-id> --reply-to <message-id>` and the same stdin form. Use `--body-file <path>` for an existing long body. Do not resend after `accepted`: that means stored by the …
Read the whole file at its exact version.
How to install
mdr add appshapes/brigade/team-messaging@sha256:3a7905c65bd9840eThe line at the top of this page pins the label git:20261019.64f6b60, 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_ijxqcvyrdycsmzi4)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 19, 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 (6589 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_ijxqcvyrdycsmzi4 GET https://markdownregistry.com/api/v1/resolve?ref=appshapes/brigade/team-messaging GET https://markdownregistry.com/api/v1/blob/3a7905c65bd9840e3c98ed68b523208e9d60eb1498ca6301a16600f567fbf479
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