us-business-english

jezweb/claude-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jezweb/claude-skills --skill us-business-english
0 commentsdiscussion
summary

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.

skill.md

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:

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.

how to use us-business-english

How to use us-business-english on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add us-business-english
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jezweb/claude-skills --skill us-business-english

The skills CLI fetches us-business-english from GitHub repository jezweb/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/us-business-english

Reload or restart Cursor to activate us-business-english. Access the skill through slash commands (e.g., /us-business-english) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.574 reviews
  • Arya Nasser· Dec 28, 2024

    Useful defaults in us-business-english — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ava Gonzalez· Dec 16, 2024

    Keeps context tight: us-business-english is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Dhruvi Jain· Dec 12, 2024

    us-business-english has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Aisha Flores· Dec 12, 2024

    us-business-english has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Layla Shah· Dec 4, 2024

    We added us-business-english from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Layla Nasser· Nov 23, 2024

    us-business-english fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Yuki Mehta· Nov 19, 2024

    I recommend us-business-english for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Aisha Ramirez· Nov 7, 2024

    us-business-english has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Oshnikdeep· Nov 3, 2024

    Keeps context tight: us-business-english is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Olivia Okafor· Nov 3, 2024

    Keeps context tight: us-business-english is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 74

1 / 8