PluginBench
Skill
Pass
Audit score 90

aussie-business-english

jezweb/claude-skills

How to install aussie-business-english

npx skills add https://github.com/jezweb/claude-skills --skill aussie-business-english
Claude Code
Cursor
Windsurf
Cline
Full instructions (SKILL.md)

Source of truth, from jezweb/claude-skills.


name: aussie-business-english description: "Australian business English writing style for professional communications — warm, direct, EN-AU spelling (colour, organise, centre). Use whenever the user is writing for an Australian audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text."

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)

PatternAustralianNot
-ourcolour, favour, honour, behaviourcolor, favor
-iseorganise, realise, specialise, recogniseorganize, realize
-recentre, fibre, metre, theatrecenter, fiber
-encelicence (noun), defence, offencelicense (noun)
-ise/-izeBoth technically valid in AU, prefer -ise
Double Ltravelling, cancelling, modellingtraveling

Noun/verb splits:

NounVerb
licencelicense
practicepractise
adviceadvise

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.

ContextFormalityGreetingSign-off
Slack/Teams (internal)Casual"Hey" / first nameNone needed
Email to existing clientFriendly professional"Hi [Name]""Cheers" / "Thanks"
Email to new clientProfessional"Hi [Name]""Kind regards" / "Thanks"
Proposal or quoteProfessional"Hi [Name]""Kind regards"
Follow-up after meetingFriendly professional"Hi [Name]""Cheers" / "Talk soon"
Cold outreachWarm professional"Hi [Name]""Cheers" / "Thanks"
Formal letter or legalFormal"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:

  1. Cheers — default, works almost everywhere
  2. Thanks — when you're asking for something or appreciating effort
  3. Kind regards — one step more formal, good for new clients
  4. Regards — neutral, slightly cooler
  5. 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 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"
"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

  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. Don't overdo 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. Specific over vague. "I'll have this to you by Thursday" not "I'll get back to you soon."

  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:

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.

Related skills

More from jezweb/claude-skills and the wider catalog.

AWaward-application logo

award-application

jezweb/claude-skills

Write compelling award submissions, grant applications, and competition entries. Maps achievements to selection criteria using evidence-based narratives. Use whenever the user is applying for a business award (Telstra, chamber of commerce, industry awards), a grant, a competition, or any submission demonstrating merit against defined criteria.

694 installs
CLcloudflare-api logo

cloudflare-api

jezweb/claude-skills

Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide resource audits. Produces curl commands or scripts. Triggers: 'cloudflare api', 'bulk dns', 'custom hostname', 'email routing', 'cache purge', 'waf rule', 'd1 query', 'r2 bucket', 'kv bulk', 'vectorize query', 'audit resources', 'fleet operation'.

745 installsAudited
CLcloudflare-worker-builder logo

cloudflare-worker-builder

jezweb/claude-skills

Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax, API route conflicts, HMR issues, or deployment failures.

1.2k installs
COcolor-palette logo

color-palette

jezweb/claude-skills

Generate accessible 11-shade colour palettes and Tailwind themes from a single brand hex.

2.4k installsAudited
D1d1-drizzle-schema logo

d1-drizzle-schema

jezweb/claude-skills

Generate Drizzle ORM schemas for Cloudflare D1 with correct D1-specific patterns and migrations.

1.3k installs
D1d1-migration logo

d1-migration

jezweb/claude-skills

Cloudflare D1 migration workflow: generate with Drizzle, inspect SQL for gotchas, apply to local and remote, fix stuck migrations, handle partial failures. Use when running migrations, fixing migration errors, or setting up D1 schemas.

876 installsAudited