Aussie Business English Skill for Claude
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/jezweb/claude-skills --skill aussie-business-englishThe instruction itself
5 sections, as written by the authorAussie 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
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take jezweb/aussie-business-english from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.