Corporate Communication
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.
Install
/plugin marketplace add surendranb/writing-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add surendranb/writing-skills --skill corporate-communicationgit clone --depth 1 https://github.com/surendranb/writing-skills.git /tmp/writing-skills
mkdir -p ~/.claude/skills
cp -r /tmp/writing-skills/skills/corporate-communication ~/.claude/skills/corporate-communicationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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.Details
- Skill name
corporate-communication- Repository
- surendranb/writing-skills
- Path
skills/corporate-communication/SKILL.md- License
- MIT
- Repo updated
- 2 September 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Corporate Communication skill do?
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.
How do I install the Corporate Communication skill?
Claude Code plugin: /plugin marketplace add surendranb/writing-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Corporate Communication popular?
It lives in surendranb/writing-skills, which has 55 GitHub stars and 3 forks, and is included in 1 curated skill list.
Related skills
Asd Ste100
55surendranb/writing-skills
Use when writing technical procedures, instructions, warnings, maintenance manuals, or any text where every reader including non-native English speakers must understand exactly one meaning.
Bob Ross
55surendranb/writing-skills
Write calm, soothing, gently instructional prose in the voice of Bob Ross. Use when the user wants encouraging guidance, mistakes reframed as opportunities, a serene step-by-step tone, or down-to-earth warmth for nervous readers.
Business Writing
55surendranb/writing-skills
Write executive-grade business communication with BLUF (bottom line up front), active verbs, and zero buzzwords. Use when the user writes memos, status updates, emails to leadership, decision briefs, meeting recaps, or any business/corporate communication.
Google Dev Docs
55surendranb/writing-skills
Use when writing API documentation, READMEs, tutorials, reference guides, error messages, or any technical content for developers using the Google developer documentation style guide.
Build Flow
49crewAIInc/skills
Building CrewAI Flows on crewai 1.15.x: structured (Pydantic) vs dict state and state.id, @start/@listen/@router wiring, or_/and_ semantics, router labels vs method names, @persist (correct import, where it stores state, restore_from_state_id), checkpointing with CheckpointConfig, @human_feedback and HumanFeedbackResult.feedback, plot(), calling crews and agents from flow methods, kickoff inputs, and the `crewai create flow` scaffold. Use when writing or debugging a Flow subclass or main.py with `from crewai.flow import ...`, when a listener never fires or fires twice, or when you see errors l
Gov Uk Style
55surendranb/writing-skills
Use when writing public-facing content, government or civic communication, help pages, policy summaries, or content requiring maximum-scope readability according to GOV.UK standards.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.