TypingMindTypingMindThe best frontend for AI
Pmstudio Comms logo

Pmstudio Comms

Community
coco-research
pmstudio-comms

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.

Overview

Publishercoco-research
Repositorycoco
Skill namepmstudio-comms
Stars
550
Forks
12
Bundled files
1
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by coco-research on GitHub. Read the source before you install it.

Installation

Install the Pmstudio Comms AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/coco-research/coco/tree/main/skills/stakeholder-comms
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/coco-research/coco.git /tmp/coco
mkdir -p .claude/skills
cp -r /tmp/coco/skills/stakeholder-comms .claude/skills/pmstudio-comms
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Pmstudio Comms in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Pmstudio Comms on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Pmstudio Comms is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

CommandTemplateWhen to Use
/stakeholder-comms go-liveGo-Live AnnouncementProduct/feature launching
/stakeholder-comms statusStatus UpdatePeriodic reporting (weekly/biweekly)
/stakeholder-comms onboard {name}Onboarding BriefNew team member joining
/stakeholder-comms changeChange NotificationPlanned change to live product
/stakeholder-comms incidentIncident SummaryPost-incident communication
/stakeholder-comms steercoSteerCo UpdateLeadership/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:

TemplateAdditional Sources
Go-LivePRD (scope, success metrics), Meeting-Notes (launch decisions)
StatusPRD (milestones, timeline), Meeting-Notes (recent), Change-Log (recent entries)
OnboardStakeholder Directory, PRD (overview), Presentations (links to share)
ChangePRD (affected components), DR-Plan (rollback procedures if exists)
IncidentIRP (severity definitions if exists), Meeting-Notes (incident details)
SteerCoPRD (timeline, risks), Change-Log (period changes), all recent Meeting-Notes

Step 3: Ask Clarifying Questions

Only ask what can't be inferred from context:

  • Audience: Who receives this? (all stakeholders / specific group / leadership)
  • Tone: Formal (board) / professional (cross-team) / casual (own team)
  • Period: For status updates — what date range?
  • Specific content: For incident — what happened? For change — what's changing?

Step 4: Generate Communication

Output location: Comms/{Type}-{Date}-{Audience}.md

If Comms/ directory doesn't exist, create it.

Templates

See references/templates.md for the full template content for each type. Summary:

Go-Live Announcement
  • Subject line, TL;DR (2 sentences), What's Live (scope), Who It Affects, What To Do (action items per audience group), Known Limitations, Support Contacts, Timeline (what's next)
Status Update
  • Period, RAG Status (Red/Amber/Green with explanation), Key Accomplishments (bulleted), Decisions Made, Risks & Blockers (with owners), Upcoming Milestones (next 2 weeks), Action Items (table: item/owner/due), Help Needed
Onboarding Brief
  • Welcome, Product Overview (2-paragraph summary), Your Role, Key Contacts (table: name/role/email/when-to-contact), Access Setup Checklist, Key Documents (links), First-Week Actions, Glossary (10 most-used terms)
Change Notification
  • What's Changing, When, Why, Who's Affected, What You Need To Do, Rollback Plan, Support Contacts
Incident Summary
  • Severity, Timeline (bullet list: detected/responded/resolved), Impact, Root Cause, Resolution, Prevention (what we're doing so this doesn't happen again), Action Items
SteerCo Update
  • Executive Summary (3 bullets max), RAG Status with trend arrow, Decisions Needed (numbered, with context and recommendation), Budget & Timeline (table), Key Risks (top 3 with mitigation status), Accomplishments Since Last SteerCo, Next Period Focus

Step 5: Present and Refine

Show the generated communication. Ask:

  • "Ready to save, or would you like to adjust anything?"
  • For emails: "Want me to include a subject line suggestion?"

Critical Rules

  1. Use real data. Pull actual names, dates, and scope from project files. Never use placeholders like "[Name]" if the information exists in context.
  2. Appropriate detail level. SteerCo updates are concise (1 page). Onboarding briefs are comprehensive. Match the template.
  3. Action-oriented. Every communication should make clear what the reader should DO. No information-only dumps.
  4. Tone matching. Leadership comms use formal language. Team comms can be direct. Incident comms are factual and calm.
  5. Don't fabricate. If you don't have incident details, ask. Don't guess root causes or timelines.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Pmstudio Comms AI skill do?

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.

Why use Pmstudio Comms on TypingMind?

Because you install it once and use it with any model. Pmstudio Comms is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Pmstudio Comms in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/coco-research/coco/tree/main/skills/stakeholder-comms. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Pmstudio Comms?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Pmstudio Comms?

As many as you like. As long as a model supports skills, you can use Pmstudio Comms with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Pmstudio Comms AI skill free?

It is published on GitHub by coco-research. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
obra logo

Executing Plans

obra
CommunityPopular

Use when you have a written implementation plan to execute in a separate session with review checkpoints

25.8K
288.1K
Instructions
View
obra logo

Using Superpowers

obra
CommunityPopular

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

25.8K
288.1K
5 files
View
affaan-m logo

Context And Decisions

affaan-m
CommunityPopular

Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require…

41.4K
277.3K
2 files
View
affaan-m logo

Docs Governance

affaan-m
CommunityPopular

Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks…

41.4K
277.3K
4 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇