Skip to content
Agentmart
Submit a tool

corporate-communication

Write internal corporate communications — announcements, org changes, policy updates, launch messages — with clarity, honesty, and calibrated warmth.

Skill by surendranb

IndexedMIT★ 50
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/surendranb-corporate-communication

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Write internal corporate communications — announcements, org changes, policy updates, launch messages — with clarity, honesty, and calibrated warmth. Use when the user writes company-wide emails, leadership messages, change communications, or sensitive internal news.

Use cases: writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/corporate-communication

What's inside

Skill name
corporate-communication
Description
Write internal corporate communications — announcements, org changes, policy updates, launch messages — with clarity, honesty, and calibrated warmth. Use when the user writes company-wide emails, leadership messages, change communications, or sensitive internal news.
License
MIT
Instructions
44 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# 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

1. **Announcement first, context second.** No preamble, no "I'm writing to share". The news is the first sentence.
2. **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.
3. **Honest uncertainty.** If details are pending, say so in one line ("we'll share specifics by Friday"). Never fill a gap with vague reassurance.
4. **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.
5. **One action per reader.** End with the single thing the reader should do or expect next.
6. **Normal-human register.** First person plural, contractions allowed, no corporate boilerplate ("we remain committed to", "as part of our ongoing efforts").
7. **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?

## Do not

- Spin, hedge, or bury bad news in good news ("we're excited to announce... as we unfortunately...")
- Announce before the humans involved have been told
- Write a wall of process when the reader needs impact and next steps

## Example transformations

**Before:** "As we continue to evolve our operating model to better serve customers in an ever-changing market, we are pleased to announce a strategic realignment of our go-to-market organization, which will enable greater focus and agility going forward. We remain committed to our employees throughout this transformation."

**After:** "We are combining our sales and customer-success teams into one organization, effective August 1. Why: customers told us handoffs between the two teams lose work, and we are losing renewals because of it. What it means for you: your manager and role are unchanged; your goals will be updated by next week. One team, one shared renewal number. We'll walk through the new structure at all-hands on Thursday."

**Before:** "It is with mixed emotions that we inform you that due to restructuring initiatives, certain positions will be impacted."

**After:** "We are eliminating 40 roles across engineering and marketing, effective September 15. This is the hardest decision we've made as a company. Everyone affected is being told today, personally, by their manager — with severance, benefits through January, and six months of placement support. For everyone else: your role is unchanged, and we will be honest with you as we learn what happens next."

From surendranb/writing-skills, MIT.

More from surendranb/writing-skills

Signals

Stars
50
Forks
3
Open issues
0
Last commit (this folder)
Aug 14, 2026 (2 months ago)
Last release
Sep 2, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from surendranb

Cite this page

corporate-communication skill. Agent Mart. https://agentmart.dev/skills/surendranb-corporate-communication (last updated 2026-10-24)