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
With your agent
Install OMGSkills skill "surendranb/writing-skills:skills/corporate-communication" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/surendranb/writing-skills /tmp/writing-skills && ln -s /tmp/writing-skills/skills/corporate-communication ~/.claude/skills/corporate-communication
From README
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.
More from this repo
asd-ste100
Used when writing technical procedures, instructions, warnings, maintenance manuals, or any text where every reader...
business-writing
Used to write executive-grade business communication with BLUF (bottom line up front), active verbs, and zero buzzwords.
google-dev-docs
Used when writing API documentation, READMEs, tutorials, reference guides, error messages, or any technical content for...
