本文へ移動
cccskills
無料GitHub で公開

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, or any business writing. Apply to drafting, editing, and tone-checking professional text.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md8.1 KB

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)

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Generate AI images using Gemini or GPT APIs directly. Covers model selection (Gemini for scenes; GPT Image 2 for text rendering, batch variations, multi-reference compositing; GPT Image 1.5 for transparent icons), the 5-part prompting framework, API calling patterns, multi-turn editing, and quality assurance. Produces photorealistic scenes, icons, illustrations, OG images, posters, infographics, and product shots. Use when building websites that need images, creating marketing assets, or generating visual content. Triggers: 'generate image', 'ai image', 'create hero image', 'make an icon', 'generate illustration', 'create og image', 'poster', 'infographic', 'image variations', 'gpt-image-2', 'ai art', 'image generation'.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

app-docs

無料

Generate complete user documentation for a web app with screenshots. Browses the app via browser automation, screenshots every screen, and produces a structured user guide with step-by-step instructions, annotated screenshots, workflow diagrams, and reference tables. Supports quick (key screens), standard (all pages), thorough (every state and flow), and exhaustive (publishable documentation suite). Triggers: 'document the app', 'user guide', 'app documentation', 'screenshot docs', 'generate user docs', 'help docs', 'how-to guide', 'write the docs'.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

Australian business English for professional writing — warm, direct, EN-AU spelling (colour, organise, centre), no filler words. Use whenever the user is writing for an Australian audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

Write compelling award submissions, grant applications, and competition entries. Maps achievements to selection criteria using evidence-based narratives. Use whenever the user is applying for a business award (Telstra, chamber of commerce, industry awards), a grant, a competition, or any submission demonstrating merit against defined criteria.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide resource audits. Produces curl commands or scripts. Triggers: 'cloudflare api', 'bulk dns', 'custom hostname', 'email routing', 'cache purge', 'waf rule', 'd1 query', 'r2 bucket', 'kv bulk', 'vectorize query', 'audit resources', 'fleet operation'.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax, API route conflicts, HMR issues, or deployment failures.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

jezweb のスキルをすべて見る

このスキルの問題を報告する