Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

nz-business-english新西兰商务英语

Agent Skill

nz-business-english 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

9,384

周安装

391

GitHub Stars

750

下载量

3,128
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:nz-business-english(新西兰商务英语)
来源仓库:https://github.com/jezweb/claude-skills
仓库路径:skills/nz-business-english
安装命令:
npx skills add https://github.com/jezweb/claude-skills --skill nz-business-english
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jezweb/claude-skills --skill nz-business-english

简介

nz-business-english 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。
  • 通过 npx 命令从指定 GitHub 仓库安装,需确认权限和维护状态。
  • 使用前应检查是否会触发联网、命令执行或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

NZ Business English

Professional but approachable. Warm without being over-the-top. Inclusive by default. Write like a competent Kiwi professional -- not like an Australian pretending to be from New Zealand, not like someone who just discovered Te Reo, and not like a corporate drone.

NZ English is close to Australian English in spelling and register, but softer in tone, more collaborative in framing, and increasingly incorporates Te Reo Maori in everyday business use.

Spelling (EN-NZ)

EN-NZ follows the same conventions as EN-AU:

PatternNew ZealandNot
-ourcolour, favour, honour, behaviourcolor, favor
-iseorganise, realise, specialise, recogniseorganize, realize
-recentre, fibre, metre, theatrecenter, fiber
-encelicence (noun), defence, offencelicense (noun), defense
Double Ltravelling, cancelling, modellingtraveling, canceling

Noun/verb splits:

NounVerb
licencelicense
practicepractise
adviceadvise

NZ-specific vocabulary:

NZ termAU/US equivalent
diarycalendar / schedule
ringcall / phone
fortnighttwo weeks (uncommon in US)
bach (North Island) / crib (South Island)holiday house
whanaufamily / team (Te Reo, widely understood)

Date format: Day Month Year, no comma -- 15 January 2026. Same as UK/AU convention.

Te Reo Maori in Business

Te Reo greetings and phrases are increasingly standard in NZ business, especially in government, education, and community-facing organisations. Use them naturally, not performatively.

PhraseUse
Kia oraGeneral greeting -- equivalent to "Hi". Safe default for any context.
Kia ora [Name]Personal greeting. Widely used in emails.
Nga mihi"With thanks / regards" -- common sign-off
Nga mihi nui"With great thanks" -- warmer, for appreciative contexts
Morena"Good morning" -- informal, internal comms
Ka pai"Good / well done" -- informal acknowledgement

When to use: Match the organisation's culture. Government and iwi organisations expect it. Corporate clients may or may not use it -- follow their lead. When in doubt, "Kia ora" as a greeting is universally appropriate in NZ.

When not to use: Don't sprinkle random Te Reo words through otherwise English text for decoration. Use complete phrases that you understand the meaning of.

Tone Ladder

Match formality to context. Default to "warm professional" -- a touch softer and more collaborative than Australian.

ContextFormalityGreetingSign-off
Slack/Teams (internal)Casual"Hey" / "Kia ora"None needed
Email to existing clientWarm professional"Kia ora [Name]" / "Hi [Name]""Cheers" / "Nga mihi"
Email to new clientProfessional"Kia ora [Name]" / "Hi [Name]""Kind regards" / "Nga mihi"
Proposal or quoteProfessional"Kia ora [Name]""Kind regards" / "Nga mihi"
Follow-up after meetingWarm professional"Hi [Name]""Cheers" / "Thanks"
Cold outreachWarm professional"Kia ora [Name]" / "Hi [Name]""Kind regards"
Formal letter or legalFormal"Dear [Name]""Yours sincerely" / "Nga mihi"

Never use: "Dear Sir/Madam" (unless legal/unknown), "Warmest regards", "Respectfully yours".

Sign-off Ranking

From most to least common in NZ SME context:

  1. Cheers -- default, works almost everywhere
  2. Nga mihi -- warm, culturally appropriate, increasingly standard
  3. Thanks -- when asking for something or appreciating effort
  4. Kind regards -- one step more formal, good for new clients
  5. Regards -- neutral, slightly cooler

Avoid: "Best" (reads as American), "Warm regards" (overdone), "Ta" (too casual for written comms).

Avoid List

Foreign Corporate-isms

Replace these reflexively:

Instead ofWrite
"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"
"deliverables""what we'll provide" / "the work"
"align on""agree on" / "sort out"

Forced Kiwi-isms

Avoid in written professional comms:

  • "Sweet as", "choice", "mean as" -- spoken slang, not business writing
  • "Bro" / "cuz" -- casual spoken, inappropriate in professional writing
  • "She'll be right" -- fine spoken, dismissive in writing about real issues
  • "Chur" -- very informal, not for business emails
  • Overuse of Te Reo for decoration -- use phrases you understand, not random words
  • "No worries" for serious issues -- fine for acknowledgements, wrong for "Your site has been offline for two days"

Australian-isms That Don't Apply

  • "Arvo", "brekkie", "barbie" -- Australian slang, not NZ
  • "G'day" -- distinctly Australian, not Kiwi
  • "Fair dinkum" -- Australian, not used in NZ

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 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. Collaborative framing. NZ business culture skews collaborative. "We could look at this together" rather than "I'll handle this". "What do you think?" is a natural closer.
  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 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:

Kia ora 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 sorted by end of next week. I'll send through a preview link once it's live on the staging site. Cheers, [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 favourable response at your earliest convenience.

Right tone:

Kia ora 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. Nga mihi, [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.

Right tone:

Kia ora 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 put you in touch with a couple of people who might be able to help sooner. Cheers, [Your name]

Context Rules

Corporate clients: Match their formality up one notch but keep the warmth. "Kind regards" instead of "Cheers", but still "Kia ora [Name]" or "Hi [Name]" not "Dear Mr Smith". Never mirror their jargon back.

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.

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. State GST position (inclusive/exclusive) explicitly -- NZ GST is 15%.

Saying no: Respectful and brief. Give the reason (one sentence), offer an alternative if possible. Don't over-explain or apologise excessively. "Put you in touch with" is more Kiwi than "recommend".

Following up: Casual but purposeful. "Just checking in on this" is fine. "I trust this email finds you well" is not.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.2%
按下载量换算1,132

Claude

29.71%
按下载量换算929

Cursor

20.75%
按下载量换算649

Gemini CLI

9.74%
按下载量换算305

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills