Skip to content
Development
Skill

/us-business-english

American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy,

From plugin
jezweb-skills
1k63 skills57 commands
Install
$ npx -y skills add jezweb/claude-skills --skill us-business-english --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/us-business-english

Context preview

The summary Claude sees to decide when to auto-load this skill.

American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy,

SKILL.md

us-business-english.SKILL.md
name: us-business-english
description: "American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text."

US Business English

Professional and direct. Confident without being pushy. Friendly without being sloppy. Write like a competent American professional who gets things done -- not like a Silicon Valley bro, not like a Wall Street memo, and not like a corporate buzzword machine.

Spelling (EN-US)

| Pattern | American | Not | |---------|----------|-----| | -or | color, favor, honor, behavior | colour, favour | | -ize | organize, realize, specialize, recognize | organise, realise | | -er | center, fiber, meter, theater | centre, fibre | | -ense | license (noun and verb), defense, offense | licence (noun), defence | | Single L | traveling, canceling, modeling | travelling, cancelling | | -og | catalog, dialog, analog | catalogue, dialogue | | -ment | judgment, acknowledgment | judgement, acknowledgement |

**Noun/verb note:** Unlike British/Australian English, American English uses "license" and "practice" for both noun and verb forms. No split needed.

**Common traps:** inquiry (standard, not enquiry), curb (road edge), tire (wheel), program (all contexts), check (not cheque), gray (not grey).

**Date format:** Month Day, Year -- January 15, 2026. Use this in all written communications unless matching a specific system format.

Tone Ladder

Match formality to context. Default to "professional friendly" -- clear and personable.

| Context | Formality | Greeting | Sign-off | |---------|-----------|----------|----------| | Slack/Teams (internal) | Casual | "Hey" / first name | None needed | | Email to existing client | Professional friendly | "Hi [Name]" | "Best" / "Thanks" | | Email to new client | Professional | "Hi [Name]" | "Best" / "Thanks" | | Proposal or quote | Professional | "Hi [Name]" | "Best regards" / "Best" | | Follow-up after meeting | Professional friendly | "Hi [Name]" | "Thanks" / "Talk soon" | | Cold outreach | Warm professional | "Hi [Name]" | "Best" / "Thanks" | | Formal letter or legal | Formal | "Dear [Name]" | "Sincerely" |

**Never use:** "Dear Sir/Madam" (unless truly unknown recipient in legal context), "Warmest regards", "Respectfully yours" (reserve for military/government), "Cheers" (reads as affected British).

Sign-off Ranking

From most to least common in US SME context:

1. **Best** -- default, works almost everywhere 2. **Thanks** -- when you're asking for something or appreciating effort 3. **Best regards** -- one step more formal, good for proposals 4. **Regards** -- neutral, slightly cooler 5. **Talk soon** -- casual, signals ongoing relationship

**Avoid:** "Cheers" (sounds British/Australian to American ears), "Kind regards" (slightly stiff), "Warm regards" (overdone), "Respectfully" (government/military tone).

Avoid List

Corporate Buzzwords

Replace these reflexively:

| Instead of | Write | |-----------|-------| | "synergy" / "synergize" | "working together" / "combined effort" | | "leverage" (verb) | "use" / "take advantage of" | | "circle back" | "follow up" / "come back to this" | | "touch base" | "check in" / "connect" | | "loop in" | "include" / "bring in" | | "bandwidth" (for time) | "time" / "capacity" | | "actionable insights" | "useful information" / "what we found" | | "move the needle" | "make a difference" / "improve" | | "deep dive" | "closer look" / "detailed review" | | "pivot" | "change direction" / "adjust" | | "align on" | "agree on" / "get on the same page" | | "unpack" (an idea) | "look at" / "go through" | | "cadence" | "schedule" / "frequency" | | "deliverables" | "what we'll provide" / "the work" |

Foreign-isms and Overcorrections

Avoid in written professional comms:

  • **"Whilst", "amongst"** -- use "while", "among"
  • **"Shall"** -- use "will" or "should"
  • **"Keen"** -- use "interested" or "excited about"
  • **"Brilliant" / "lovely"** -- sounds British, use "great" / "sounds good"
  • **"Dude", "awesome", "totally"** in formal emails -- fine on Slack, not in proposals
  • **Forced casualness** -- "Hey buddy!" to a new client is too much

Writing Principles

1. **Lead with the point.** First sentence answers the question or states the purpose. Context comes after, not before.

2. **Short paragraphs.** Two to three sentences max. One idea per paragraph. White space is your friend.

3. **Natural contractions.** "We've", "I'll", "that's", "won't" -- reads human. Ease off slightly in proposals, but emails should sound like a person wrote them.

4. **Active voice.** "We'll send the report Monday" not "The report will be sent on Monday."

5. **Specific over vague.** "I'll have this to you by Thursday" not "I'll get back to you soon."

6. **One ask per email.** Multiple requests? Number them. Don't bury the second ask in paragraph four.

7. **Match their energy.** Short email from client? Short reply. Detailed brief? Detailed response. Don't write five paragraphs when two lines will do.

Examples

Status update to existing client

**Too corporate:** > Dear Mr. Thompson, I am writing to provide you with a comprehensive update regarding the current status of your website redesign project. Please find below a summary of the deliverables completed to date and the anticipated timeline for remaining action items moving forward.

**Right tone:** > Hi David, > > Quick update on the website -- we've finished the homepage and the three main service pages. Everything's looking solid. > > Next up is the contact form and booking system, which we'll have ready by end of next week. I'll send over a preview link once it's live on the staging site. > > Best, > [Your name]

Delivering a quote

**Too stiff:

Read more
Ships withjezweb-skills

Production workflow skills for Claude Code. Each skill guides Claude through a recipe to produce tangible output — scaffolded projects, generated assets, professional documents, deployed services. Ten plugins of practical, production-oriented skills.

Get the whole plugin

Other skills on jezweb-skills.