Skip to main content
skill CX Codex

corporate-communication — Claude Code skill: setup and usage

Drafts internal announcements, leadership memos, and org updates with direct clarity and zero corporate boilerplate.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add surendranb/writing-skills --skill corporate-communication -a claude-code
Open on GitHub

What corporate-communication does

This skill strips corporate fluff from internal memos. The formula is straightforward. The announcement comes in the very first sentence without opening pleasantries. Readers learn immediately why a decision happened and what changes for their team. If specific details remain undecided, the text states that directly instead of offering empty reassurance.

The underlying checklist bans evasive corporate jargon. Terms like restructuring or synergy are replaced with exact counts of eliminated roles. Warmth is strictly calibrated. Difficult news receives plain respect rather than cheerful reframing. Installation relies on Node.js to run npx or a manual copy of SKILL.md into your agent directory.

What it helps with

  • eliminate euphemisms when announcing layoffs or reorganizations
  • draft all-hands updates about department merges and process shifts
  • explain the exact impact of leadership decisions on employees
  • define a single clear action step for readers at the end of a memo

Example prompts for the agent

  • Draft a company-wide email announcing the closure of a project and role eliminations using corporate-communication rules.
  • Rewrite this reorganization announcement to remove corporate spin and state clearly what changes for employees.
  • Write a leadership memo moving performance reviews to twice a year, keeping it under five sentences.

How to install corporate-communication

1Skills CLI (Vercel)

npx skills add surendranb/writing-skills --skill corporate-communication -a claude-code

2Manually: put the files in place

~/.claude/skills/corporate-communication/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/corporate-communication/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about corporate-communication

How do I install corporate-communication in Claude Code?

Run npx skills add surendranb/writing-skills --skill corporate-communication -a claude-code in your terminal. You can also place the file directly at ~/.claude/skills/corporate-communication/SKILL.md.

What is the corporate-communication skill used for?

It structures internal announcements and leadership memos to avoid corporate spin. The prompt forces the core news into the opening sentence and directly clarifies what changes for readers.

Which words does the corporate-communication skill forbid?

It forbids evasive terms like "restructuring" and "synergy" when roles are eliminated. It also bans conversational warmups like "I'm writing to share" and cheerful reframing of bad news.

Source text

SKILL.md · MIT
---
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.
---

# 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."

© surendranb · MIT · surendranb/writing-skills

Similar skills

All skills for Writing and docs →

From the same set16

orwells-rules This skill edits drafts using Orwell’s six writing rules, trimming clichés and excess words while favoring active voice. Use it to revise prose written by you or an agent. CX Codex +1 ★ 53repo stars journalism-ap A skill that holds the agent to Associated Press conventions when drafting news copy and press releases: attribution, numbers, dates, no editorializing. Useful when the text has to read as factual reporting. CX Codex +1 ★ 53repo stars jack-sparrow Rewrites plain announcements and updates into theatrical pirate prose inspired by Captain Jack Sparrow. Fits launch notes, status copy, and playful messages. CX Codex +1 ★ 53repo stars gov-uk-style This skill applies GOV.UK writing principles to public-facing content. Use it to revise help pages, service information, or policy summaries. CX Codex +1 ★ 53repo stars google-dev-docs A skill that makes the agent write technical docs the Google way: action headings, second person, present tense, active voice. Useful for READMEs, tutorials and API references. CX Codex +1 ★ 53repo stars business-writing This skill structures memos, leadership emails, status updates, and decision briefs around a clear takeaway. Use it when a draft needs a direct ask and supporting facts. CX Codex +1 ★ 53repo stars asd-ste100 Enforces ASD-STE100 Simplified Technical English rules for procedures and manuals so readers grasp the exact intended meaning without confusion. CX Codex +1 ★ 53repo stars skill-folder-name A writing-skill template for defining style rules, checks, prohibitions, and before-and-after examples. Use it when prose needs repeatable guidance. CX Codex +1 ★ 53repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor