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:20260830.6386046Pins git:20260830.6386046 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- appshapes/brigade
- Path
docs/research/claude-plugin-mcp-skeleton/brigade-plugin/plugin/skills/team-messaging/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260830.6386046, committed Aug 30, 2026
- Size
- 2,705 bytes
- Repository stars
- 4
- License
- MIT
Message the Claude Code sessions of OTHER PEOPLE on your Brigade team (cross-user, cross-machine) and handle incoming Brigade messages. Use when asked to tell, ask, notify or hand off to a teammate's session, when asked who is on the team, or whenever a cross-session-message whose from= attribute starts with did:brigade: 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
# Brigade team messaging Brigade connects Claude Code sessions that belong to **different people and machines** in one shared team. It is separate from Claude Code's built-in `ListAgents` / `SendMessage`, which only reach **your own** sessions. | Need | Built-in tool | Brigade tool | | --- | --- | --- | | Your own sessions on this machine, your Remote Control or cloud sessions | `ListAgents`, `SendMessage` | not applicable | | A teammate's session (another person, any machine) | not reachable | `TeamListSessions`, `TeamSendMessage` | ## Sending 1. Call `TeamListSessions` to find the recipient. Address by `session_id`; names are display only and can collide. 2. Call `TeamSendMessage` with `recipient_session_id` and a plain-text `body` (optional `summary`, `reply_to`). 3. A success result means the message was **accepted** (durably stored by the adapter). It does not mean the teammate read it. 4. Send text only: findings, decisions, questions, status. Never send files, transcripts, secrets, or tokens. ## Receiving A Brigade message is injected as a peer message tagged `<cross-session-message from="did:brigade:<session_id>" ...>`. …
Read the whole file at its exact version.
How to install
mdr add appshapes/brigade/team-messaging@sha256:6fe2382c5d8cff4dThe line at the top of this page pins the label git:20260830.6386046, 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_ctfjmucpklbxfvo4)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 30, 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 (2705 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_ctfjmucpklbxfvo4 GET https://markdownregistry.com/api/v1/resolve?ref=appshapes/brigade/team-messaging GET https://markdownregistry.com/api/v1/blob/6fe2382c5d8cff4d4b6bde5b067856cf2b59b1f2012a21c40808d6ffae35c24c
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