us-business-english by jezweb/claude-skills
npx skills add https://github.com/jezweb/claude-skills --skill us-business-english专业且直接。自信但不咄咄逼人。友好但不随意。写作风格应像一位有能力、能成事的美国专业人士——既不像硅谷兄弟会成员,也不像华尔街备忘录,更不像企业流行语机器。
| 模式 | 美式 | 非美式 |
|---|---|---|
| -or | color, favor, honor, behavior | colour, favour |
| -ize | organize, realize, specialize, recognize | organise, realise |
| -er | center, fiber, meter, theater | centre, fibre |
| -ense | license (名词和动词), defense, offense | licence (名词), defence |
| 单 L | traveling, canceling, modeling | travelling, cancelling |
| -og | catalog, dialog, analog | catalogue, dialogue |
| -ment | judgment, acknowledgment | judgement, acknowledgement |
与英式/澳大利亚英语不同,美式英语使用 "license" 和 "practice" 同时作为名词和动词形式。无需区分。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
常见陷阱: inquiry (标准,非 enquiry), curb (路边), tire (轮胎), program (所有语境), check (非 cheque), gray (非 grey)。
日期格式: 月 日, 年 -- January 15, 2026。在所有书面沟通中使用此格式,除非需要匹配特定系统格式。
根据语境匹配正式程度。默认为"专业友好型"——清晰且亲切。
| 语境 | 正式程度 | 问候语 | 结尾敬语 |
|---|---|---|---|
| Slack/Teams (内部) | 随意 | "Hey" / 名字 | 无需 |
| 给现有客户的邮件 | 专业友好 | "Hi [姓名]" | "Best" / "Thanks" |
| 给新客户的邮件 | 专业 | "Hi [姓名]" | "Best" / "Thanks" |
| 提案或报价 | 专业 | "Hi [姓名]" | "Best regards" / "Best" |
| 会议后跟进 | 专业友好 | "Hi [姓名]" | "Thanks" / "Talk soon" |
| 陌生客户开发 | 热情专业 | "Hi [姓名]" | "Best" / "Thanks" |
| 正式信函或法律文件 | 正式 | "Dear [姓名]" | "Sincerely" |
切勿使用: "Dear Sir/Madam" (除非在法律语境中确实未知收件人), "Warmest regards", "Respectfully yours" (保留给军事/政府), "Cheers" (听起来像做作的英式表达)。
在美国中小企业语境中,从最常见到最不常见:
避免使用: "Cheers" (在美国人听来像英式/澳大利亚式), "Kind regards" (略显生硬), "Warm regards" (过度), "Respectfully" (政府/军事语气)。
下意识地替换这些词:
| 替换掉 | 应写作 |
|---|---|
| "synergy" / "synergize" | "working together" / "combined effort" |
| "leverage" (动词) | "use" / "take advantage of" |
| "circle back" | "follow up" / "come back to this" |
| "touch base" | "check in" / "connect" |
| "loop in" | "include" / "bring in" |
| "bandwidth" (指时间) | "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" (一个想法) | "look at" / "go through" |
| "cadence" | "schedule" / "frequency" |
| "deliverables" | "what we'll provide" / "the work" |
在书面专业沟通中避免:
开门见山。 第一句话就回答问题或说明目的。背景信息放在后面,而不是前面。
段落简短。 最多两到三句话。一个段落一个观点。留白是你的朋友。
自然的缩略形式。 "We've", "I'll", "that's", "won't" -- 读起来像人写的。在提案中可以稍微减少使用,但邮件应该听起来像人写的。
主动语态。 "We'll send the report Monday" 而不是 "The report will be sent on Monday."
具体而非模糊。 "I'll have this to you by Thursday" 而不是 "I'll get back to you soon."
一封邮件一个请求。 多个请求?给它们编号。不要把第二个请求埋在第四段里。
匹配对方的能量。 客户邮件简短?简短回复。简报详细?详细回应。两行字就能搞定的时候,不要写五段。
过于企业化:
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.
正确语气:
Hi David,
关于网站的最新情况——我们已经完成了主页和三个主要服务页面。一切看起来都很不错。
接下来是联系表单和预订系统,我们将在下周末前准备好。一旦在暂存站点上线,我会发一个预览链接给你。
Best, [你的名字]
过于生硬:
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.
正确语气:
Hi Sarah,
谢谢昨天的通话——很高兴能清楚地了解你的需求。
我根据我们讨论的内容整理了一份报价。简而言之:整个网站,包括预订系统,费用是 $4,500。这涵盖了设计、开发和上线到你的域名。
如果你有任何问题,随时可以电话沟通。
Best, [你的名字]
过于直接:
We can't do that.
过于委婉:
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.
正确语气:
Hi Mark,
谢谢你考虑我们来做这件事。遗憾的是,我们目前无法承接——直到三月份我们的时间都排满了。
如果时间合适,我们很乐意在四月份看看。否则,我可以推荐几个可能更快帮上忙的人。
Best, [你的名字]
企业客户: 将正式程度提高一级,但要保持清晰和人性化。用 "Best regards" 而不是 "Best",但仍然是 "Hi [姓名]" 而不是 "Dear Mr. Smith"。切勿模仿他们的行话——如果他们说 "synergize",你就说 "work together"。
传达坏消息: 直接但要友善。陈述问题,简要解释原因,提供解决方案。不要废话,不要过度道歉。一句 "sorry" 就够了——两句显得歉疚,三句就是卑躬屈膝。
报价: 直接且自信。"The cost for this is $X" 而不是 "We would like to propose a fee of $X for your consideration." 说明包含的内容。不要含糊其辞。使用美元金额,除非国际语境需要,否则不加 "USD"。
拒绝: 尊重且简洁。给出理由(一句话),如果可能的话提供替代方案。不要过度解释或过度道歉。
跟进: 随意但有目的性。"Just checking in on this" 没问题。"I trust this email finds you well" 不行。"Wanted to bump this to the top of your inbox" 也可以。
每周安装数
123
代码仓库
GitHub 星标数
643
首次出现
12 天前
安全审计
安装于
opencode119
kimi-cli118
gemini-cli118
amp118
cline118
github-copilot118
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.
| 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.
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]" |
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).
From most to least common in US SME context:
Avoid: "Cheers" (sounds British/Australian to American ears), "Kind regards" (slightly stiff), "Warm regards" (overdone), "Respectfully" (government/military tone).
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" |
Avoid in written professional comms:
Lead with the point. First sentence answers the question or states the purpose. Context comes after, not before.
Short paragraphs. Two to three sentences max. One idea per paragraph. White space is your friend.
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.
Active voice. "We'll send the report Monday" not "The report will be sent on Monday."
Specific over vague. "I'll have this to you by Thursday" not "I'll get back to you soon."
One ask per email. Multiple requests? Number them. Don't bury the second ask in paragraph four.
Match their energy. Short email from client? Short reply. Detailed brief? Detailed response. Don't write five paragraphs when two lines will do.
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]
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]
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]
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.
Weekly Installs
123
Repository
GitHub Stars
643
First Seen
12 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode119
kimi-cli118
gemini-cli118
amp118
cline118
github-copilot118
谈判录用通知与薪酬策略指南 - 3位产品领导者教你高效谈判技巧
789 周安装
Binance子账户API开发指南 - 虚拟账户创建、期货期权管理、资产查询
924 周安装
FlowStudio MCP 构建部署 Power Automate 云流指南 | 自动化流程开发
933 周安装
Python PDF 提取技能:使用 pdfplumber 库精确提取文本、表格和元数据
1,000 周安装
Laravel安全最佳实践指南 | 防范CSRF、SQL注入、XSS攻击
1,200 周安装
生产排程实战指南:离散制造工厂的有限产能排程、换线优化与瓶颈管理
1,200 周安装
AI代码审查工具 - 自动化安全漏洞检测与代码质量分析 | 支持多领域检查清单
1,200 周安装
| "Sincerely" |
| "deliverables" | "what we'll provide" / "the work" |