A writing skill for producing internal company messages such as status updates, stakeholder reports, newsletters, FAQs, and incident reports. It can use available team, issue-tracking, calendar, and document sources, or ask for missing context.

Use it to draft project updates, leadership reports, company newsletters, FAQ answers, and incident reports for different audiences.

It provides consistent formats and helps gather the information needed for a clear update when some sources are unavailable.

write-comms — Skill for Claude Code by samkawsarani

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add samkawsarani/sams-product-plugins --skill write-comms

Clone the repo

git clone --depth 1 https://github.com/samkawsarani/sams-product-plugins

Made for: Claude Code.

Or install write-comms, the plugin that ships this one along with the rest of its 1 skill.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/write-comms/github.svg)](https://agentmods.dev/skills/samkawsarani/sams-product-plugins/write-comms)

Your own site

<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/write-comms"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/write-comms/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/write-comms"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/write-comms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,445 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00075	$0.01445
Opus 5.5	$0.00030	$0.00578
Sonnet 5.5	$0.00015	$0.00289
Haiku 4.5	$0.00007	$0.00145

Measured 2mo ago against content hash 8e948ebcdd9b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-comms scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/write-comms/skills/write-comms/SKILL.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Available Sources

Check which data sources are present — the skill works with any combination. For each missing source, ask the user to provide that context directly instead.

Slack MCP: available → pull team updates and announcements | missing → ask user for key updates
Linear MCP: available → pull completed issues, milestones, blockers | missing → ask user for project status
gws CLI (command -v gws): available → pull calendar events via gws calendar +agenda | missing → ask user for meeting highlights
Google Drive MCP: available → pull recently published docs | missing → ask user for relevant documents

Proceed regardless of which sources are missing. Never stop due to an unavailable data source.

Internal Communications Writer

Generate clear, actionable internal communications that keep teams aligned and leadership informed.

Quick Start

Common triggers:

"Write a 3P update for [team]"
"Create a stakeholder update for [project]"
"Draft a company newsletter"
"Write FAQ answers for [topic]"
"Create a status report for [audience]"
"Write an incident report for [issue]"

Communication Types

Type	Audience	Read Time	Reference File
3P Update	Team leads, execs	30-60 sec	`references/3p-updates.md`
Stakeholder Update	Executives, leadership	5-10 min	`references/stakeholder-updates.md`
Company Newsletter	All employees	3-5 min	`references/company-newsletter.md`
FAQ Answers	All employees	1-2 min per Q	`references/faq-answers.md`
General Comms	Varies	Varies	`references/general-comms.md`

Core Workflow

1. Gather Context

Before writing any communication:

Identify the type — Match the request to a communication type above
Load the reference file — Read the corresponding file from references/
Clarify scope — Confirm with the user:
- Team or project name
- Target audience
- Time period covered
- Desired tone (if not standard)
Check voice guide — Check for a voice/style guide if one exists

Read the full file on GitHub · 143 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 143 lines · 75 tokens per session scan A 8e948ebcdd9b

Subscribe to this mod's changes

write-comms is a skill published in the GitHub repository samkawsarani/sams-product-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 1,445 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Writing and docs

write-comms next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
write-commssamkawsarani/sams-product-plugins	Skill	2	1mo ago	MIT	A	75	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	today	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	99k	today	Apache-2.0	A	19	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
chat-pet-sprite-creationmicrosoft/vscode	Skill	195k	today	MIT	A	53	Claude Code, Codex