pmstudio-comms skillA
pmstudio-comms is agent-read markdown (skill) from coco-research/coco: Generate templated stakeholder communications from project context. Use when someone asks to "write a go-live email", "create a status update", "onboard someone", "write an announcement", "steerco update", "incident summary", "change notification", or any stakeholder communication task. Reads project memory, stakeholder directory, PRD, and meeting notes to pre-fill real names, dates, and context. Produces ready-to-send Markdown..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Stakeholder Comms — Templated Communications Generator
## Purpose
Generates stakeholder communications pre-filled with project context. Not generic templates — these pull real stakeholder names, real dates, real scope from project artifacts.
## Process
### Step 1: Identify Template
From user request or by asking:
| Command | Template | When to Use |
|---------|----------|-------------|
| `/stakeholder-comms go-live` | Go-Live Announcement | Product/feature launching |
| `/stakeholder-comms status` | Status Update | Periodic reporting (weekly/biweekly) |
| `/stakeholder-comms onboard {name}` | Onboarding Brief | New team member joining |
| `/stakeholder-comms change` | Change Notification | Planned change to live product |
| `/stakeholder-comms incident` | Incident Summary | Post-incident communication |
| `/stakeholder-comms steerco` | SteerCo Update | Leadership/governance meeting prep |
If no subcommand, ask: "What type of communication do you need?"
### Step 2: Read Context
**All templates read:**
- `CLAUDE.local.md` — project overview, key decisions, stakeholders, recent changes
- `.sync-watch.json` — project name
**Template-specific reads:**
…Read the whole file at its exact version.
How to install
mdr add coco-research/coco/pmstudio-comms@git:20260802.1479e32mdr add coco-research/coco/pmstudio-comms@sha256:3d523bcb3af40599Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_xue6ernctrvxil6v)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260802.1479e32 latest | 2026-08-02 | 1479e32 | 4,992 B | A | view · diff |
| git:20260426.d53cc6c | 2026-04-26 | d53cc6c | 4,981 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 (4992 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
coco-research/coco · 478 stars · license NOASSERTION · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xue6ernctrvxil6v GET https://markdownregistry.com/api/v1/resolve?ref=coco-research/coco/pmstudio-comms GET https://markdownregistry.com/api/v1/blob/3d523bcb3af40599a30c7e757f4097ec5a302b4164bcb8df16bfe291958e9e7f
Your agent 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.