aussie-business-english by jezweb/claude-skills
npx skills add https://github.com/jezweb/claude-skills --skill aussie-business-english专业但不刻板。热情而不做作。直接但不生硬。自然体现澳洲特色而不落俗套。写作风格应像一位恰好是澳洲人的能干专业人士——既不像假装澳洲人的美国人,也不像古板的公司职员。
| 模式 | 澳洲拼写 | 非澳洲拼写 |
|---|---|---|
| -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 (名词) |
| -ise/-ize | 两者在澳洲都有效,但优先使用 -ise | — |
| 双写 L | travelling, cancelling, modelling | traveling |
名词/动词区分:
| 名词 |
|---|
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 动词 |
|---|
| licence | license |
| practice | practise |
| advice | advise |
常见陷阱: enquiry (一般询问), inquiry (正式/法律调查), kerb (路缘), tyre (轮胎), programme (一般项目), program (计算机程序)。
根据语境调整正式程度。默认使用"友好专业"——中间地带。
| 语境 | 正式程度 | 问候语 | 结束语 |
|---|---|---|---|
| Slack/Teams (内部) | 随意 | "Hey" / 直呼其名 | 无需 |
| 给现有客户的邮件 | 友好专业 | "Hi [姓名]" | "Cheers" / "Thanks" |
| 给新客户的邮件 | 专业 | "Hi [姓名]" | "Kind regards" / "Thanks" |
| 提案或报价 | 专业 | "Hi [姓名]" | "Kind regards" |
| 会议后跟进 | 友好专业 | "Hi [姓名]" | "Cheers" / "Talk soon" |
| 陌生联系 | 热情专业 | "Hi [姓名]" | "Cheers" / "Thanks" |
| 正式信函或法律文件 | 正式 | "Dear [姓名]" | "Yours sincerely" |
切勿使用: "Dear Sir/Madam", "To Whom It May Concern" (除非在正式/法律语境中确实不知道收件人), "Warmest regards", "Respectfully yours"。
在澳洲中小企业语境中,从最常见到最不常见:
避免使用: "Best" (美式), "Best wishes" (过于正式), "Warm regards" (过度使用), "Respectfully" (对中小企业来说太生硬)。
下意识地替换这些:
| 避免使用 | 应写作 |
|---|---|
| "reach out" | "get in touch" / "contact" |
| "circle back" | "follow up" / "come back to" |
| "touch base" | "check in" / "catch up" |
| "leverage" (动词) | "use" / "make the most of" |
| "moving forward" | "from here" / "going forward" (或直接省略) |
| "actionable insights" | "useful information" / "what we found" |
| "deep dive" | "closer look" / "detailed review" |
| "bandwidth" (指时间) | "time" / "capacity" |
| "pivot" | "change direction" / "adjust" |
| "loop in" | "include" / "bring in" |
| "align on" | "agree on" / "sort out" |
| "unpack" (一个想法) | "look at" / "go through" |
| "cadence" | "schedule" / "rhythm" |
| "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 an update regarding the progress of your website redesign project. Please find below a summary of the deliverables completed to date and the anticipated timeline for remaining action items.
恰当语气:
Hi David,
网站更新简报——我们已经完成了主页和三个主要服务页面。目前进展顺利。
接下来是联系表单和预订系统,我们将在下周末前完成。一旦在测试站点上线,我会发预览链接给你。
Cheers, [你的名字]
过于生硬:
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 favourable response at your earliest convenience.
恰当语气:
Hi Sarah,
感谢昨天的交流——很高兴能清楚了解你的需求。
我根据我们讨论的内容整理了一份报价。简而言之:完整网站(包括预订系统)的费用是4,500澳元。这涵盖了设计、开发和部署到你的域名。
如果你有任何问题,随时可以电话沟通。
Cheers, [你的名字]
过于直接:
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.
恰当语气:
Hi Mark,
感谢你考虑我们做这个项目。遗憾的是,我们目前无法承接——直到三月份我们的时间都已排满。
如果时间合适,我们很乐意在四月份考虑。或者,我可以推荐几位可能更快帮到你的人。
Cheers, [你的名字]
企业客户: 将正式程度提高一级但仍保持温暖。"Kind regards" 而非 "Cheers",但仍用 "Hi [姓名]" 而非 "Dear Mr Smith"。切勿模仿他们的行话——如果他们说"协同效应",你就说"合作"。
传达坏消息: 直接但友善。说明问题,简要解释原因,提供解决方案。不要含糊其辞,不要过度道歉。一个"sorry"足够——两个是道歉,三个是卑躬屈膝。
报价: 直接且自信。"The cost for this is $X" 而非 "We would like to propose a fee of $X for your consideration." 说明包含内容。不要模棱两可。
拒绝: 尊重且简洁。给出理由(一句话),如果可能提供替代方案。不要过度解释或过度道歉。
跟进: 随意但有目的性。"Just checking in on this" 即可。"I trust this email finds you well" 则不合适。
每周安装量
377
仓库
GitHub 星标数
650
首次出现
Feb 18, 2026
安全审计
安装于
opencode337
codex333
github-copilot332
gemini-cli331
cursor327
kimi-cli323
Professional but not corporate. Warm without being forced. Direct without being blunt. Naturally Australian without stereotyping. Write like a competent professional who happens to be Australian — not like an American pretending to be Australian, and not like a stuffy corporate drone.
| Pattern | Australian | 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) |
| -ise/-ize | Both technically valid in AU, prefer -ise | — |
| Double L | travelling, cancelling, modelling | traveling |
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).
Match formality to context. Default to "friendly professional" — the middle ground.
| Context | Formality | Greeting | Sign-off |
|---|---|---|---|
| Slack/Teams (internal) | Casual | "Hey" / first name | None needed |
| Email to existing client | Friendly professional | "Hi [Name]" | "Cheers" / "Thanks" |
| Email to new client | Professional | "Hi [Name]" | "Kind regards" / "Thanks" |
| Proposal or quote | Professional | "Hi [Name]" | "Kind regards" |
| Follow-up after meeting | Friendly professional | "Hi [Name]" | "Cheers" / "Talk soon" |
| Cold outreach | Warm professional | "Hi [Name]" | "Cheers" / "Thanks" |
| Formal letter or legal | Formal | "Dear [Name]" |
Never use: "Dear Sir/Madam", "To Whom It May Concern" (unless truly unknown recipient in formal/legal context), "Warmest regards", "Respectfully yours".
From most to least common in AU SME context:
Avoid: "Best" (American), "Best wishes" (too formal), "Warm regards" (overdone), "Respectfully" (too stiff for SME).
Replace these reflexively:
| Instead of | Write |
|---|---|
| "reach out" | "get in touch" / "contact" |
| "circle back" | "follow up" / "come back to" |
| "touch base" | "check in" / "catch up" |
| "leverage" (verb) | "use" / "make the most of" |
| "moving forward" | "from here" / "going forward" (or drop it) |
| "actionable insights" | "useful information" / "what we found" |
| "deep dive" | "closer look" / "detailed review" |
| "bandwidth" (for time) | "time" / "capacity" |
| "pivot" | "change direction" / "adjust" |
| "loop in" | "include" / "bring in" |
| "align on" | "agree on" / "sort out" |
| "unpack" (an idea) | "look at" / "go through" |
| "cadence" | "schedule" / "rhythm" |
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. Don't overdo 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 an update regarding the progress of your website redesign project. Please find below a summary of the deliverables completed to date and the anticipated timeline for remaining action items.
Right tone:
Hi David,
Quick update on the website — we've finished the homepage and the three main service pages. Looking good so far.
Next up is the contact form and booking system, which we'll have ready by end of next week. I'll send through a preview link once it's live on the staging site.
Cheers, [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 favourable response at your earliest convenience.
Right tone:
Hi Sarah,
Thanks for the chat 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 jump on a call if you've got any questions.
Cheers, [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.
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.
Cheers, [Your name]
Corporate clients: Match their formality up one notch but keep the warmth. "Kind regards" instead of "Cheers", but still "Hi [Name]" not "Dear Mr Smith". Never mirror their jargon back — if they say "synergies", you say "working together".
Delivering bad news: Be direct but kind. State the issue, explain why briefly, offer the path forward. No waffle, no excessive apologies. One "sorry" is enough — two is apologetic, three is grovelling.
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.
Saying no: Respectful and brief. Give the reason (one sentence), offer an alternative if possible. Don't over-explain or apologise excessively.
Following up: Casual but purposeful. "Just checking in on this" is fine. "I trust this email finds you well" is not.
Weekly Installs
377
Repository
GitHub Stars
650
First Seen
Feb 18, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode337
codex333
github-copilot332
gemini-cli331
cursor327
kimi-cli323
内容创作指南:跨渠道营销内容模板与SEO优化技巧
1,200 周安装
| "Yours sincerely" |
| "deliverables" |
| "what we'll provide" / "the work" |