nz-business-english
New Zealand business English writing style for professional communications — warm, inclusive, EN-NZ spelling (colour, organise, centre). Use whenever the user is writing for a New Zealand audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.
- Installs
- 920
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jezweb/claude-skills --skill nz-business-english- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads nz-business-english automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
| Pattern | New Zealand | 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 |
| Double L | travelling, cancelling, modelling | traveling, canceling |
Noun/verb splits:
| Noun | Verb |
|---|---|
| licence | license |
| practice | practise |
| advice | advise |
NZ-specific vocabulary:
| NZ term | AU/US equivalent |
|---|---|
| diary | calendar / schedule |
| ring | call / phone |
| fortnight | two weeks (uncommon in US) |
| bach (North Island) / crib (South Island) | holiday house |
| whanau | family / 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.
| Phrase | Use |
|---|---|
| Kia ora | General 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.
| Context | Formality | Greeting | Sign-off |
|---|---|---|---|
| Slack/Teams (internal) | Casual | "Hey" / "Kia ora" | None needed |
| Email to existing client | Warm professional | "Kia ora [Name]" / "Hi [Name]" | "Cheers" / "Nga mihi" |
| Email to new client | Professional | "Kia ora [Name]" / "Hi [Name]" | "Kind regards" / "Nga mihi" |
| Proposal or quote | Professional | "Kia ora [Name]" | "Kind regards" / "Nga mihi" |
| Follow-up after meeting | Warm professional | "Hi [Name]" | "Cheers" / "Thanks" |
| Cold outreach | Warm professional | "Kia ora [Name]" / "Hi [Name]" | "Kind regards" |
| Formal letter or legal | Formal | "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:
- Cheers -- default, works almost everywhere
- Nga mihi -- warm, culturally appropriate, increasingly standard
- Thanks -- when asking for something or appreciating effort
- Kind regards -- one step more formal, good for new clients
- 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 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" |
| "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
-
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 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."
-
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.
-
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.
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.
FAQ
What does the nz-business-english skill do?
New Zealand business English writing style for professional communications — warm, inclusive, EN-NZ spelling (colour, organise, centre). Use whenever the user is writing for a New Zealand audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.
How do I install nz-business-english?
Run npx skills add https://github.com/jezweb/claude-skills --skill nz-business-english in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/nz-business-english/ (personal) or .claude/skills/nz-business-english/ (project).
Which AI agents can use nz-business-english?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is nz-business-english safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains nz-business-english?
It is published by jezweb in jezweb/claude-skills. It has 920 recorded installs.
More from jezweb/claude-skills
shadcn-ui
jezweb/claude-skills
Install and configure shadcn/ui components for React projects. Guides component selection, installation order, dependency management, customisation with semantic tokens, and common UI recipes (forms, data tables, navigation, modals). Use after tailwind-theme-builder has set up the theme infrastructure, when adding components, building forms, creating data tables, or setting up navigation.
color-palette
jezweb/claude-skills
Generate complete, accessible colour palettes from a single brand hex. Produces 11-shade scale (50-950), semantic tokens, dark mode variants, Tailwind v4 CSS output, WCAG contrast checks. Use whenever the user supplies a brand hex and asks for a palette, mentions setting up a design system, wants Tailwind theme colours from a brand colour, or asks to check colour accessibility / contrast.
tailwind-theme-builder
jezweb/claude-skills
Set up Tailwind v4 + shadcn/ui themed UI with dark mode. Install deps, configure CSS variables via @theme inline, wire dark mode toggle, verify. Use whenever the user mentions Tailwind v4, setting up Tailwind theming, shadcn/ui colours, dark mode, or troubleshooting colours not working, tw-animate-css errors, @theme inline conflicts, @apply breaking after upgrade, or v3 → v4 migration issues.
wordpress-elementor
jezweb/claude-skills
Edit Elementor pages and manage templates on WordPress sites via browser automation (for visual / structural changes) or WP-CLI (for safe text replacements). Use whenever the user wants to edit an Elementor page, update text in Elementor widgets, apply or manage Elementor templates, or make content changes to pages built with the Elementor page builder.
ux-audit
jezweb/claude-skills
Walk through a live web app AS a real user to find usability + behavioural bugs that static reviews miss. REQUIRES proof of interaction (typing, clicking, sending, observing) before any verdict — a sweep that didn't interact terminates with verdict 'Incomplete'. Walks threads, exercises every element, runs the multi-pane stress matrix, visual polish sweep, component perfection checklist, automated a11y (axe-core), pragmatic performance budget (LCP/CLS/INP), scenario battery (11 scenarios), and stress recipes including the real-flavour data battery. Hard gates: console errors/warnings = 0, network 5xx = 0, layout collapse = 0, axe Critical/Serious = 0, perf budget green. Audit-the-audit meta-check rejects rushed reports. Each finding has reproduction steps, evidence path, and suspected code location. Trigger with 'ux audit', 'walkthrough', 'qa sweep', 'audit the app', 'dogfood this', 'check all pages', 'find what's broken', 'stress the UI'.
tailwind-v4-shadcn
jezweb/claude-skills
Set up Tailwind v4 with shadcn/ui using @theme inline pattern and CSS variable architecture. Four-step pattern: CSS variables, Tailwind mapping, base styles, automatic dark mode. Prevents 8 documented errors. Use when initializing React projects with Tailwind v4, or fixing colors not working, tw-animate-css errors, @theme inline dark mode conflicts, @apply breaking, v3 migration issues.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.