uk-business-english by jezweb/claude-skills
npx skills add https://github.com/jezweb/claude-skills --skill uk-business-english专业且审慎。礼貌而不谄媚。直接而不唐突。自然体现英式风格而非刻板印象。写作应像一位恰好是英国人的专业能手——既非狄更斯笔下的人物,也非美国科技初创公司的口吻,更非那种刚学会用"whilst"一词的人。
| 模式 | 英式 | 非英式 |
|---|---|---|
| -our | colour, favour, honour, behaviour | color, favor |
| -ise | organise, realise, specialise, recognise | organize, realize |
| -re | centre, fibre, metre, theatre | center, fiber |
| -ence | licence (名词), defence, offence | license (名词), defense |
| -ise/-ize | 英式英语两者皆可;为保持一致性建议使用 -ise | — |
| 双写 L | travelling, cancelling, modelling | traveling, canceling |
| -ogue | catalogue, dialogue, analogue | catalog, dialog |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| -ement |
| judgement, acknowledgement |
| judgment (仅限法律语境) |
名词/动词区分:
| 名词 | 动词 |
|---|---|
| licence | license |
| practice | practise |
| advice | advise |
常见易错词: enquiry(一般询问),inquiry(正式/法律调查),kerb(路缘),tyre(轮胎),programme(一般项目),program(计算机程序),cheque(支票),grey(非 gray)。
日期格式: 日 月 年,不加逗号——2026年1月15日。缩写:2026年1月15日。切勿使用月/日/年格式。
根据语境匹配正式程度。默认采用"礼貌专业"语气——比澳大利亚或美国英语基准稍正式,但仍保持亲切感。
| 语境 | 正式程度 | 问候语 | 结束语 |
|---|---|---|---|
| Slack/Teams(内部) | 随意 | "Hi" / 直呼其名 | 无需 |
| 邮件给现有客户 | 礼貌专业 | "Hi [姓名]" | "Kind regards" / "Thanks" |
| 邮件给新客户 | 专业 | "Dear [姓名]" / "Hi [姓名]" | "Kind regards" |
| 提案或报价 | 专业 | "Dear [姓名]" | "Kind regards" / "Yours sincerely" |
| 会议后跟进 | 礼貌专业 | "Hi [姓名]" | "Kind regards" / "Thanks" |
| 陌生联系 | 专业 | "Dear [姓名]" / "Hi [姓名]" | "Kind regards" |
| 正式信函或法律文件 | 正式 | "Dear [姓名]" / "Dear Sir or Madam" | "Yours sincerely" / "Yours faithfully" |
规则: 知道对方姓名时用"Yours sincerely"。不知道时(用Dear Sir or Madam开头)用"Yours faithfully"。用错会显得粗心。
切勿使用: 首次联系时用"Hey","To Whom It May Concern"(改用"Dear Sir or Madam"),"Warmest regards","Respectfully yours"。
在英国中小企业语境中从最常见到最少见:
避免: 单独使用"Best"(显得美式),首次联系用"Cheers"(建立融洽关系后可用),"Warm regards"(过度使用),"Ta"(书面语中过于随意)。
下意识替换这些:
| 改用 | 应写为 |
|---|---|
| "reach out" | "get in touch" / "contact" |
| "touch base" | "catch up" / "check in" |
| "circle back" | "come back to" / "follow up" |
| "leverage" (动词) | "use" / "make the most of" |
| "moving forward" | "going forward" / "from here" (或直接省略) |
| "actionable insights" | "useful findings" / "what we found" |
| "deep dive" | "closer look" / "detailed review" |
| "bandwidth" (指时间) | "time" / "capacity" |
| "gotten" | "got" |
| "could care less" | "couldn't care less" |
| "loop in" | "include" / "copy in" |
| "deliverables" | "what we'll provide" / "the work" |
| "Monday through Friday" | "Monday to Friday" |
| "on the team" | "in the team" |
专业书面沟通中避免:
开门见山。 首句即回答问题或阐明目的。背景信息放在后面,而非开头。英式礼貌不意味着埋没重点。
段落简短。 最多两到三句话。每段一个核心思想。留白是你的朋友。
适度使用缩略形式。 邮件中"We've"、"I'll"、"that's"均可接受。提案和正式信函中减少使用。目标是人性化而非机械化——但基准比美式或澳式英语稍正式。
主动语态。 "We'll send the report on Monday"而非"The report will be dispatched on Monday."
具体而非模糊。 "I'll have this to you by Thursday"而非"I'll revert at my earliest convenience."
每封邮件一个请求。 多个请求?请编号。勿将第二个请求埋在第四段。
轻描淡写而非夸大其词。 "That's quite a good result"比"That's an absolutely incredible, game-changing result!"效果更好。克制彰显自信。
过于企业化:
尊敬的汤普森先生,谨此告知您网站改版项目的当前进展。随函附上迄今已完成交付成果的总结及剩余工作计划的预计时间表。
恰当语气:
Hi David,
网站进度简报——我们已完成首页和三个主要服务页面。整体进展顺利。
接下来是联系表单和预订系统,预计下周完成。上线测试环境后我会发送预览链接。
Kind regards,[您的姓名]
过于生硬:
尊敬的客户,随函附上根据讨论范围拟定的正式报价单。望此方案能获您认可,并期待在您方便时收到积极回复。
恰当语气:
Hi Sarah,
感谢昨日的通话——很高兴明确了您的需求。
我已根据讨论内容拟定了报价。简而言之:完整网站(含预订系统)费用为3,500英镑。涵盖设计、开发及域名部署。
如有疑问,随时可安排通话沟通。
Kind regards,[您的姓名]
过于直接:
我们无法处理此事。
过于委婉:
尽管我们非常重视您的垂询并十分期待进一步探讨此方向,但遗憾的是目前我们无法满足此项具体请求。
恰当语气:
Hi Mark,
感谢您考虑我们承接此事。遗憾的是目前我们无法接手——三月份前已排满日程。
若时间合适,我们很乐意四月份再行商议。或者,我可推荐几家能更快响应的公司供您参考。
Kind regards,[您的姓名]
企业客户: 匹配其正式程度但保持自身清晰度。若对方使用"Dear [姓名]"和"Yours sincerely",可相应采用。切勿模仿其行话——若对方说"key learnings going forward",你应说"what we've found"。
传达坏消息: 直接但体贴。说明问题,简要解释,提供解决方案。英式礼貌意味着妥善措辞,但勿用过多修饰语掩盖核心信息。一句"apologies"足矣。
报价: 清晰自信。"The cost for this is GBP X"而非"We would wish to propose a fee of GBP X for your kind consideration."明确包含内容。清晰说明增值税处理方式(含税/不含税)。
拒绝: 礼貌简洁。"Unfortunately"已足够——无需三句铺垫。说明理由,如有可能提供替代方案。
跟进: 目的明确但不强求。"Just checking in on this"即可。"I trust this finds you well"是套话——建议省略。"Wanted to bring this back to the top of your inbox"可以接受。
每周安装量
108
代码仓库
GitHub 星标数
643
首次出现
11 天前
安全审计
安装于
opencode105
kimi-cli104
gemini-cli104
amp104
cline104
github-copilot104
Professional and measured. Polite without being obsequious. Direct without being abrupt. Naturally British without being a caricature. Write like a competent professional who happens to be British -- not like a Dickens character, not like an American tech startup, and not like someone who just discovered the word "whilst".
| Pattern | British | Not |
|---|---|---|
| -our | colour, favour, honour, behaviour | color, favor |
| -ise | organise, realise, specialise, recognise | organize, realize |
| -re | centre, fibre, metre, theatre | center, fiber |
| -ence | licence (noun), defence, offence | license (noun), defense |
| -ise/-ize | Both accepted in GB; prefer -ise for consistency | — |
| Double L | travelling, cancelling, modelling | traveling, canceling |
| -ogue | catalogue, dialogue, analogue | catalog, dialog |
| -ement | judgement, acknowledgement | judgment (legal only) |
Noun/verb splits:
| Noun | Verb |
|---|---|
| licence | license |
| practice | practise |
| advice | advise |
Common traps: enquiry (general), inquiry (formal/legal), kerb (road edge), tyre (wheel), programme (general), program (computing), cheque (payment), grey (not gray).
Date format: Day Month Year, no comma -- 15 January 2026. Abbreviated: 15 Jan 2026. Never Month/Day/Year.
Match formality to context. Default to "polite professional" -- a step more formal than Australian or American baseline, but still warm.
| Context | Formality | Greeting | Sign-off |
|---|---|---|---|
| Slack/Teams (internal) | Casual | "Hi" / first name | None needed |
| Email to existing client | Polite professional | "Hi [Name]" | "Kind regards" / "Thanks" |
| Email to new client | Professional | "Dear [Name]" / "Hi [Name]" | "Kind regards" |
| Proposal or quote | Professional | "Dear [Name]" | "Kind regards" / "Yours sincerely" |
| Follow-up after meeting | Polite professional | "Hi [Name]" | "Kind regards" / "Thanks" |
| Cold outreach | Professional | "Dear [Name]" / "Hi [Name]" | "Kind regards" |
| Formal letter or legal | Formal |
Rule: "Yours sincerely" when you know their name. "Yours faithfully" when you don't (Dear Sir or Madam). Getting this wrong marks you as careless.
Never use: "Hey" in first contact, "To Whom It May Concern" (use "Dear Sir or Madam"), "Warmest regards", "Respectfully yours".
From most to least common in UK SME context:
Avoid: "Best" on its own (reads as American), "Cheers" in first contact (fine once rapport is established), "Warm regards" (overdone), "Ta" (too informal for anything written).
Replace these reflexively:
| Instead of | Write |
|---|---|
| "reach out" | "get in touch" / "contact" |
| "touch base" | "catch up" / "check in" |
| "circle back" | "come back to" / "follow up" |
| "leverage" (verb) | "use" / "make the most of" |
| "moving forward" | "going forward" / "from here" (or drop it) |
| "actionable insights" | "useful findings" / "what we found" |
| "deep dive" | "closer look" / "detailed review" |
| "bandwidth" (for time) | "time" / "capacity" |
| "gotten" | "got" |
| "could care less" | "couldn't care less" |
| "loop in" | "include" / "copy in" |
| "deliverables" | "what we'll provide" / "the work" |
| "Monday through Friday" | "Monday to Friday" |
Avoid in written professional comms:
Lead with the point. First sentence answers the question or states the purpose. Context comes after, not before. British politeness doesn't mean burying the lead.
Short paragraphs. Two to three sentences max. One idea per paragraph. White space is your friend.
Measured contractions. "We've", "I'll", "that's" are fine in emails. Use fewer in proposals and formal letters. The goal is human, not robotic -- but the baseline is slightly more formal than American or Australian English.
Active voice. "We'll send the report on Monday" not "The report will be dispatched on Monday."
Specific over vague. "I'll have this to you by Thursday" not "I'll revert at my earliest convenience."
One ask per email. Multiple requests? Number them. Don't bury the second ask in paragraph four.
Understate rather than overstate. "That's quite a good result" lands better than "That's an absolutely incredible, game-changing result!" Restraint signals confidence.
Too corporate:
Dear Mr Thompson, I write to apprise you of the current status of your website redesign project. Please find herewith a summary of deliverables completed to date and the projected timeline for the remaining programme of work.
Right tone:
Hi David,
Quick update on the website -- we've finished the homepage and the three main service pages. Coming together nicely.
Next up is the contact form and booking system, which we'll have ready by the end of next week. I'll send through a preview link once it's on the staging site.
Kind regards, [Your name]
Too stiff:
Dear Client, Please find enclosed our formal quotation for the proposed scope of works as discussed. We trust this meets with your approval and look forward to receiving your favourable 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. In short: GBP 3,500 for the full site, including the booking system. That covers design, development, and getting it live on your domain.
Happy to arrange a call if you have any questions.
Kind regards, [Your name]
Too blunt:
We can't do that.
Too soft:
Whilst we greatly appreciate your most kind enquiry and would very much welcome the opportunity to explore this avenue further, regrettably it would not be possible for us to accommodate this particular request at the present time.
Right tone:
Hi Mark,
Thanks for thinking of us for this. Unfortunately it's not something we're able to take on at the moment -- we're fully committed through March.
If timing works, we'd be happy to look at it in April. Otherwise, I can suggest a couple of firms who might be able to help sooner.
Kind regards, [Your name]
Corporate clients: Match their formality but keep your clarity. "Dear [Name]" and "Yours sincerely" if they use it. Never mirror their jargon -- if they say "key learnings going forward", you say "what we've found".
Delivering bad news: Be direct but considerate. State the issue, explain briefly, offer the path forward. British politeness means framing matters, but don't wrap bad news in so many qualifiers that the message gets lost. One "apologies" is sufficient.
Quoting prices: Clear and confident. "The cost for this is GBP X" not "We would wish to propose a fee of GBP X for your kind consideration." Include what's covered. State VAT position (inclusive/exclusive) explicitly.
Saying no: Polite and brief. "Unfortunately" does the work -- you don't need three sentences of preamble. Give the reason, offer an alternative if possible.
Following up: Purposeful but not pushy. "Just checking in on this" works. "I trust this finds you well" is filler -- drop it. "Wanted to bring this back to the top of your inbox" is fine.
Weekly Installs
108
Repository
GitHub Stars
643
First Seen
11 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode105
kimi-cli104
gemini-cli104
amp104
cline104
github-copilot104
高效一对一沟通指南:7位产品领导者的框架与技巧,提升团队管理效能
764 周安装
.NET 架构师专家 - C# ASP.NET Core 微服务与性能优化解决方案
237 周安装
Build工作流编排器:AI驱动的开发流程自动化工具,支持绿地/棕地/TDD/重构
239 周安装
设计模式实现指南:TypeScript/JavaScript 代码架构最佳实践与SOLID原则
238 周安装
aixyz on OpenClaw:无需编码部署可收费AI代理的完整指南
237 周安装
Prompt Guard v3.5.0 - 100%离线AI智能体运行时安全防护,内置600+检测模式
238 周安装
Julia编程专家指南:多重分派、类型系统与高性能计算最佳实践
89 周安装
| "Dear [Name]" / "Dear Sir or Madam" |
| "Yours sincerely" / "Yours faithfully" |
| "on the team" |
| "in the team" |