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.
npx skills add surendranb/writing-skills --skill corporate-communicationgit clone --depth 1 https://github.com/surendranb/writing-skillsWrote 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.
[](https://agentmods.dev/skills/surendranb/writing-skills/corporate-communication)<a href="https://agentmods.dev/skills/surendranb/writing-skills/corporate-communication"><img src="https://agentmods.dev/badge/skills/surendranb/writing-skills/corporate-communication/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.
<a href="https://agentmods.dev/skills/surendranb/writing-skills/corporate-communication"><img src="https://agentmods.dev/badge/skills/surendranb/writing-skills/corporate-communication.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.00838 |
| Opus 5 | $0.00025 | $0.00419 |
| Sonnet 5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
corporate-communication 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corporate Communication
Say the true thing plainly, then address the human impact. Tone serves trust.
The core rule
Clarity first, empathy second, spin never. Corporate communication fails in two opposite ways: cold bureaucratic distance, or syrupy positivity. The formula: state what changed, in plain words; state what it means for the reader; state what happens next; only then add warmth — and only if it is earned (see: earned-warmth rule — acknowledge the hard part before reframing).
Workflow: the announcement in one plain sentence → the reason, honestly (or "we can't share details yet" plainly) → what it means for you, the reader → the concrete next step → a human closing, only if genuine.
Mechanics
- Announcement first, context second. No preamble, no "I'm writing to share". The news is the first sentence.
- Name the impact explicitly. "Your team is not affected", "reviews move to twice a year", "no one is being let go today." Readers scan for impact — hand it to them.
- Honest uncertainty. If details are pending, say so in one line ("we'll share specifics by Friday"). Never fill a gap with vague reassurance.
- Calibrated warmth. Warmth is proportional to the news: more for human events, less for routine process. If the news is bad, the tone is respectful and plain, not cheerful.
- One action per reader. End with the single thing the reader should do or expect next.
- Normal-human register. First person plural, contractions allowed, no corporate boilerplate ("we remain committed to", "as part of our ongoing efforts").
- No euphemism for hard news. "Restructuring" where layoffs are involved, "rightsizing", "synergy opportunities" — banned. Say "we are eliminating 40 roles."
Verify
- First sentence contains the news (no preamble)
- Reader impact is explicit somewhere in the first half
- No euphemisms for difficult realities
- Exactly one next step or expected action
- Read the draft from the affected reader's chair: does it answer their first question?
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.
- 11d ago First seen · 48 lines · 50 tokens per session scan A 060115b946f7
corporate-communication is a skill published in the GitHub repository surendranb/writing-skills (33 stars, last pushed 9d ago), licensed MIT. It adds 50 tokens to every session and 838 once invoked, about $0.0003 per session on Opus 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-30.
Other skills, from other repositories
domscribe
Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component…
forge-connector
Guides building and deploying Atlassian Forge Teamwork Graph connector apps that ingest external data into Atlassian's Teamwork Graph, making it searchable in Rovo Search and surfaced in Rovo Chat. Use when the user wants to build a Forge connector, ingest external data into Atlassian, connect a third-party tool (e.g.…
forge-cost-optimizer
Optimizes Atlassian Forge apps to reduce platform consumption and avoid unnecessary costs using Atlassian's "Optimise Forge platform costs" guidance. Use when the user asks to optimize Forge app costs, reduce Forge invocations, lower GB-seconds, reduce storage or log usage, tune memory, replace polling, improve…
forge-app-review
Performs a lightweight pre-release readiness review of Atlassian Forge apps across manifest/module wiring, architecture, runtime compatibility, dependency posture, tests, deploy readiness, and obvious security, cost, or reliability smells. Use when the user asks "review my Forge app", "pre-deploy check", "is this app…
logic-review
Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…
logic-health
Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…