nz-business-english▌
jezweb/claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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 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.
How to use nz-business-english on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add nz-business-english
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches nz-business-english from GitHub repository jezweb/claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate nz-business-english. Access the skill through slash commands (e.g., /nz-business-english) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★55 reviews- ★★★★★Shikha Mishra· Dec 28, 2024
I recommend nz-business-english for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Noah Dixit· Dec 28, 2024
nz-business-english has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★William Singh· Dec 28, 2024
Useful defaults in nz-business-english — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kiara Liu· Dec 20, 2024
We added nz-business-english from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Mateo Sethi· Dec 16, 2024
Useful defaults in nz-business-english — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Advait Ghosh· Dec 16, 2024
nz-business-english fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kabir Martin· Dec 4, 2024
nz-business-english reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Noor Thompson· Nov 23, 2024
Registry listing for nz-business-english matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Rahul Santra· Nov 19, 2024
Solid pick for teams standardizing on skills: nz-business-english is focused, and the summary matches what you get after install.
- ★★★★★Omar Reddy· Nov 11, 2024
Useful defaults in nz-business-english — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 55