business-writing
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.
Install
With your agent
Install OMGSkills skill "surendranb/writing-skills:skills/business-writing" 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/business-writing ~/.claude/skills/business-writingFrom README
Business Writing Respect the reader's time. Verdict first, evidence after, decision-ready. The core rule BLUF — the bottom line is the first line. Executives read the first sentence; if it does not contain the answer, the rest may never be read. Every paragraph earns its place by carrying a fact, a decision, or a requested action. Workflow: one sentence: the verdict or the ask → 2–4 supporting facts with numbers → one sentence: what you need or what happens next → delete everything else. Mechanics First sentence = verdict or ask. "Q3 revenue missed by 12% and we recommend extending the campaign." If the answer is a decision, say the decision. One idea per paragraph, one decision per paragraph. If a paragraph contains two decisions, split it. Numbers over adjectives. "12% below target, $84K short" not "significantly below expectations." Active, concrete verbs. "We shipped", "I recommend", "The fix resolved". Never "it was determined that". State the ask explicitly.
More from this repo
asd-ste100
Used when writing technical procedures, instructions, warnings, maintenance manuals, or any text where every reader...
corporate-communication
Used to write internal corporate communications — announcements, org changes, policy updates, launch messages — with...
google-dev-docs
Used when writing API documentation, READMEs, tutorials, reference guides, error messages, or any technical content for...