Aussie Business EnglishSAFE

Skills for Claude Code CLI such as full stack dev Cloudflare, React, Tailwind v4, and AI integrations.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: aussie-business-english
description: "Australian business English for professional writing — warm, direct, EN-AU spelling (colour, organise, centre), no filler words. 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

Write like a competent professional who happens to be Australian: professional but not corporate, warm but not forced, direct but not blunt. Say it once, plainly, and stop.

## Non-negotiables

- **Australian spelling**: colour, organise, centre, travelling, defence. Noun/verb pairs: licence/license, practice/practise.
- **No filler words.** Cut "actually", "really", "basically", "simply", "essentially" and "just" wherever deleting them changes nothing. Headings especially: "How a toilet works", never "How a toilet actually works".
- **No AI tells.** Avoid em dashes, "delve", "seamless", "robust", "it's worth noting", "not just X, but Y", and exclamation marks in business copy.
- **Lead with the point.** First sentence carries the answer or the ask. Short paragraphs, active voice, natural contractions. Be specific: "by Thursday", not "soon".

## Tone

Default is friendly professional. Open with "Hi [Name]". Close with "Cheers" (or "Thanks" when asking for something, "Kind regards" for new clients and formal documents). Keep "Dear [Name]" and "Yours sincerely" for formal or legal letters only. Never "Dear Sir/Madam", "Best", or "Warm regards".

Match the reader: short message in, short reply out. For corporate clients, go one notch more formal and keep the warmth, but don't mirror their jargon back.

Bad news: direct and kind, one "sorry" at most, then the path forward. Saying no: brief reason, offer an alternative if you have one. Prices: state them plainly ("The cost is $4,500"), no hedging.

## Swap list

| Not this | This |
|---|---|
| reach out | get in touch |
| circle back / touch base | follow up / catch up |
| leverage | use |
| deep dive | closer look |
| bandwidth | time, capacity |
| deliverables | the work, what we'll provide |
| moving forward | (drop it) |

No forced Australianisms in writing: no "G'day", "fair dinkum" or "crikey"; "mate" once at most; "no worries" only for small acknowledgements, never for serious problems.

## The tone, in one example

> Hi Sarah,
>
> Thanks for the chat yesterday. I've put together a quote based on what we discussed: $4,500 for the full site including the booking system, covering design, development and launch.
>
> Happy to jump on a call if you've got any questions.
>
> Cheers,
> Jeremy

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.