aussie-business-english▌
jezweb/claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
$22
Aussie Business English
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.
Spelling (EN-AU)
| 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).
Tone Ladder
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]" | "Yours sincerely" |
Never use: "Dear Sir/Madam", "To Whom It May Concern" (unless truly unknown recipient in formal/legal context), "Warmest regards", "Respectfully yours".
Sign-off Ranking
From most to least common in AU SME context:
- Cheers — default, works almost everywhere
- Thanks — when you're asking for something or appreciating effort
- Kind regards — one step more formal, good for new clients
- Regards — neutral, slightly cooler
- Talk soon — casual, signals ongoing relationship
Avoid: "Best" (American), "Best wishes" (too formal), "Warm regards" (overdone), "Respectfully" (too stiff for SME).
Avoid List
American 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" |
| "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" |
| "deliverables" | "what we'll provide" / "the work" |
Forced Australianisms
Avoid in written professional comms:
- "G'day" — fine spoken, awkward in writing
- Overuse of "mate" — once is fine, every paragraph is cringe
- "No worries" for serious issues — fine for acknowledgements ("No worries, I'll sort that"), wrong for "Your server has been down for 3 days"
- "Fair dinkum", "strewth", "crikey" — never in professional writing
- "Arvo", "brekkie", "barbie" — slang, not business English
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. 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.
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:
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]
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:
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]
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:
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]
Context Rules
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.
How to use aussie-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 aussie-business-english
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches aussie-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 aussie-business-english. Access the skill through slash commands (e.g., /aussie-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.7★★★★★53 reviews- ★★★★★Chaitanya Patil· Dec 24, 2024
Solid pick for teams standardizing on skills: aussie-business-english is focused, and the summary matches what you get after install.
- ★★★★★Fatima Torres· Dec 24, 2024
We added aussie-business-english from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Valentina Martinez· Dec 16, 2024
Useful defaults in aussie-business-english — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Evelyn Farah· Dec 4, 2024
aussie-business-english has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Zaid Rao· Nov 23, 2024
aussie-business-english fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Piyush G· Nov 15, 2024
We added aussie-business-english from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Zaid Huang· Nov 15, 2024
Solid pick for teams standardizing on skills: aussie-business-english is focused, and the summary matches what you get after install.
- ★★★★★Kofi Wang· Nov 7, 2024
aussie-business-english is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Mia Robinson· Oct 26, 2024
Keeps context tight: aussie-business-english is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Zaid Srinivasan· Oct 14, 2024
We added aussie-business-english from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 53