pmstudio-comms SKILL.md skillA
pmstudio-comms from coco-research/coco is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add coco-research/coco/pmstudio-comms@git:20260802.1479e32Pins git:20260802.1479e32 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- coco-research/coco
- Path
skills/stakeholder-comms/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260802.1479e32, committed Aug 2, 2026
- First version recorded
- Apr 26, 2026
- Size
- 4,992 bytes
- Repository stars
- 797
- License
- a license file GitHub does not identify
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.
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
# 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@sha256:3d523bcb3af40599The line at the top of this page pins the label git:20260802.1479e32, 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_xue6ernctrvxil6v)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 26, 2026 and Aug 2, 2026, about one every 99 days.
| 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 · 797 stars · license a license file GitHub does not identify · pushed 2026-11-05 · 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 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.