Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jezweb avatar

Us Business English

  • 860 installs
  • 946 repo stars
  • Updated July 2, 2026
  • jezweb/claude-skills

us-business-english is a writing-style agent skill that applies direct American professional tone and EN-US spelling for developers who draft emails, proposals, client communications, and business copy for US audiences.

About

us-business-english is a jezweb/claude-skills writing guide that shapes agent output into competent, direct American business English. The skill enforces EN-US spelling (color, organize, center), confident but non-pushy tone, and action-oriented phrasing while explicitly avoiding Silicon Valley bro speak, Wall Street memo stiffness, and corporate buzzword overload. Developers invoke us-business-english when drafting or editing emails, chat messages, proposals, client communications, blog posts, and web copy for US customers and readers. The skill applies equally to fresh drafting, revision passes, and tone-checking existing professional text before send or publish.

  • Enforces EN-US spelling conventions including color/favor, organize/realize, center/meter, license/defense
  • Adapts tone to be professional, confident, action-oriented without Silicon Valley hype or corporate buzzwords
  • Applies to emails, proposals, client messages, blog posts, web copy, and chat communications
  • Covers both drafting new text and editing existing drafts for American business English
  • Handles noun/verb usage differences such as license and practice working for both forms

Us Business English by the numbers

  • 860 all-time installs (skills.sh)
  • +23 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #293 of 1,881 Documentation skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jezweb/claude-skills --skill us-business-english

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs860
repo stars946
Security audit3 / 3 scanners passed
Last updatedJuly 2, 2026
Repositoryjezweb/claude-skills

How do you write professional American business English?

Make all written output sound like a competent, direct American professional when targeting US customers, clients, or readers.

Who is it for?

Developers and technical writers producing client emails, proposals, or product copy aimed at US business readers who want consistent EN-US professional voice.

Skip if: Developers needing legal compliance review, localization into non-English markets, or highly technical API reference documentation without tone adjustment.

When should I use this skill?

The user writes for American customers, asks for US business tone, EN-US spelling, or professional email and proposal editing.

What you get

Revised emails, proposals, chat messages, blog posts, and web copy with EN-US spelling and direct US professional tone.

Files

SKILL.mdMarkdownGitHub ↗

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)

PatternAmericanNot
-orcolor, favor, honor, behaviorcolour, favour
-izeorganize, realize, specialize, recognizeorganise, realise
-ercenter, fiber, meter, theatercentre, fibre
-enselicense (noun and verb), defense, offenselicence (noun), defence
Single Ltraveling, canceling, modelingtravelling, cancelling
-ogcatalog, dialog, analogcatalogue, dialogue
-mentjudgment, acknowledgmentjudgement, 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.

ContextFormalityGreetingSign-off
Slack/Teams (internal)Casual"Hey" / first nameNone needed
Email to existing clientProfessional friendly"Hi [Name]""Best" / "Thanks"
Email to new clientProfessional"Hi [Name]""Best" / "Thanks"
Proposal or quoteProfessional"Hi [Name]""Best regards" / "Best"
Follow-up after meetingProfessional friendly"Hi [Name]""Thanks" / "Talk soon"
Cold outreachWarm professional"Hi [Name]""Best" / "Thanks"
Formal letter or legalFormal"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 ofWrite
"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:

Dear Client, Please find attached our formal quotation for the proposed scope of work as discussed. We trust this meets your requirements and look forward to your favorable response at your earliest convenience.

Right tone:

Hi Sarah,

>

Thanks for the call yesterday -- good to get a clear picture of what you need.

>

I've put together a quote based on what we discussed. The short version: $4,500 for the full site, including the booking system. That covers design, development, and getting it live on your domain.

>

Happy to hop on a call if you have any questions.

>

Best,
[Your name]

Saying no to a request

Too blunt:

We can't do that.

Too soft:

While we certainly appreciate your suggestion and would love to explore this further, unfortunately at this current juncture it may not be feasible for us to accommodate this particular request given our current bandwidth constraints.

Right tone:

Hi Mark,

>

Thanks for thinking of us for this. Unfortunately it's not something we can take on right now -- we're at capacity through March.

>

If timing works, we'd be happy to look at it in April. Otherwise, I can recommend a couple of people who might be able to help sooner.

>

Best,
[Your name]

Context Rules

Corporate clients: Match their formality up one notch but stay clear and human. "Best regards" instead of "Best", but still "Hi [Name]" not "Dear Mr. Smith". Never mirror their jargon back -- if they say "synergize", you say "work together".

Delivering bad news: Be direct but kind. State the issue, explain why briefly, offer the path forward. No filler, no excessive apologies. One "sorry" is enough -- two is apologetic, three is groveling.

Quoting prices: Direct and confident. "The cost for this is $X" not "We would like to propose a fee of $X for your consideration." Include what's covered. No hedging. Use dollar amounts without "USD" unless international context requires it.

Saying no: Respectful and brief. Give the reason (one sentence), offer an alternative if possible. Don't over-explain or apologize excessively.

Following up: Casual but purposeful. "Just checking in on this" is fine. "I trust this email finds you well" is not. "Wanted to bump this to the top of your inbox" works too.

Related skills

FAQ

When should us-business-english be applied?

us-business-english applies whenever output targets US customers or readers—emails, chat, proposals, blog posts, and web copy. Use it for drafting, editing, and tone-checking professional American business text.

What tone does us-business-english enforce?

us-business-english enforces direct, confident, friendly professional American voice with EN-US spelling. The skill avoids Silicon Valley bro tone, stiff Wall Street memo style, and empty corporate buzzwords.

Is Us Business English safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.