Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center).
Install Us Business English
$ npx skills add jezweb/claude-skills --skill us-business-english -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jezweb/claude-skills us-business-english --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/writing/skills/us-business-english .claude/skills/us-business-english && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "us-business-english" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/us-business-english into .claude/skills/us-business-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "us-business-english", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/us-business-englishType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jezweb/claude-skills --skill us-business-english -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jezweb/claude-skills us-business-english --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/writing/skills/us-business-english .agents/skills/us-business-english && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "us-business-english" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/us-business-english into .agents/skills/us-business-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "us-business-english", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jezweb/claude-skills --skill us-business-english -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jezweb/claude-skills us-business-english --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/writing/skills/us-business-english .cursor/skills/us-business-english && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "us-business-english" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/us-business-english into .cursor/skills/us-business-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "us-business-english", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jezweb/claude-skills.git --path plugins/writing/skills/us-business-english--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jezweb/claude-skills --skill us-business-english -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jezweb/claude-skills us-business-english --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/writing/skills/us-business-english .gemini/skills/us-business-english && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "us-business-english" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/us-business-english into .gemini/skills/us-business-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "us-business-english", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jezweb/claude-skills us-business-englishInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jezweb/claude-skills --skill us-business-english -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/writing/skills/us-business-english .github/skills/us-business-english && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "us-business-english" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/us-business-english into .github/skills/us-business-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "us-business-english", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jezweb/claude-skills --skill us-business-english -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jezweb/claude-skills us-business-english --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/writing/skills/us-business-english .opencode/skills/us-business-english && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "us-business-english" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/us-business-english into .opencode/skills/us-business-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "us-business-english", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
us-business-english- GitHub stars
- 1.1k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 1,089 words
- Files
- 1
- Skills in repo
- 52
- Repo updated
- First seen
- Licence
- MIT
At a glance
American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center).
- Works in 5 steps: Best -- default, works almost everywhere → Thanks -- when you're asking for… → Best regards -- one step more formal,… → …
- The user is writing for an American audience: emails
- SKILL.md covers Spelling (EN-US), Tone Ladder, Sign-off Ranking and Avoid List, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Us Business English is an agent skill from jezweb/claude-skills. American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Proposals and quotes, Blog and article writing and Brand voice and tone. The repository describes itself as: Skills for Claude Code CLI such as full stack dev Cloudflare, React, Tailwind v4, and AI integrations. The licence is MIT.
When your agent uses it
- The user is writing for an American audience: emails
- Client communications
- Any business writing
Example prompts
- “/us-business-english”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Best -- default, works almost everywhere
- Thanks -- when you're asking for something or appreciating effort
- Best regards -- one step more formal, good for proposals
- Regards -- neutral, slightly cooler
- Talk soon -- casual, signals ongoing relationship
What it can do on your machine
Read from SKILL.md and the folder at commit 1260fa7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Us Business English loads about 2.1k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 1,089 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jezweb/claude-skills at commit 1260fa7, republished under its MIT licence (© jezweb). 1,089 words, ~2,075 tokens.
Download SKILL.mdSave it as
.claude/skills/us-business-english/SKILL.md (or your agent's skills folder).- name
- us-business-english
- description
- American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.
US Business English
Professional and direct. Confident without being pushy. Friendly without being sloppy. Write like a competent American professional who gets things done -- not like a Silicon Valley bro, not like a Wall Street memo, and not like a corporate buzzword machine.
Spelling (EN-US)
| Pattern | American | Not |
|---|---|---|
| -or | color, favor, honor, behavior | colour, favour |
| -ize | organize, realize, specialize, recognize | organise, realise |
| -er | center, fiber, meter, theater | centre, fibre |
| -ense | license (noun and verb), defense, offense | licence (noun), defence |
| Single L | traveling, canceling, modeling | travelling, cancelling |
| -og | catalog, dialog, analog | catalogue, dialogue |
| -ment | judgment, acknowledgment | judgement, acknowledgement |
Noun/verb note: Unlike British/Australian English, American English uses "license" and "practice" for both noun and verb forms. No split needed.
Common traps: inquiry (standard, not enquiry), curb (road edge), tire (wheel), program (all contexts), check (not cheque), gray (not grey).
Date format: Month Day, Year -- January 15, 2026. Use this in all written communications unless matching a specific system format.
Tone Ladder
Match formality to context. Default to "professional friendly" -- clear and personable.
| Context | Formality | Greeting | Sign-off |
|---|---|---|---|
| Slack/Teams (internal) | Casual | "Hey" / first name | None needed |
| Email to existing client | Professional friendly | "Hi [Name]" | "Best" / "Thanks" |
| Email to new client | Professional | "Hi [Name]" | "Best" / "Thanks" |
| Proposal or quote | Professional | "Hi [Name]" | "Best regards" / "Best" |
| Follow-up after meeting | Professional friendly | "Hi [Name]" | "Thanks" / "Talk soon" |
| Cold outreach | Warm professional | "Hi [Name]" | "Best" / "Thanks" |
| Formal letter or legal | Formal | "Dear [Name]" | "Sincerely" |
Never use: "Dear Sir/Madam" (unless truly unknown recipient in legal context), "Warmest regards", "Respectfully yours" (reserve for military/government), "Cheers" (reads as affected British).
Sign-off Ranking
From most to least common in US SME context:
- Best -- default, works almost everywhere
- Thanks -- when you're asking for something or appreciating effort
- Best regards -- one step more formal, good for proposals
- Regards -- neutral, slightly cooler
- Talk soon -- casual, signals ongoing relationship
Avoid: "Cheers" (sounds British/Australian to American ears), "Kind regards" (slightly stiff), "Warm regards" (overdone), "Respectfully" (government/military tone).
Avoid List
Corporate Buzzwords
Replace these reflexively:
| Instead of | Write |
|---|---|
| "synergy" / "synergize" | "working together" / "combined effort" |
| "leverage" (verb) | "use" / "take advantage of" |
| "circle back" | "follow up" / "come back to this" |
| "touch base" | "check in" / "connect" |
| "loop in" | "include" / "bring in" |
| "bandwidth" (for time) | "time" / "capacity" |
| "actionable insights" | "useful information" / "what we found" |
| "move the needle" | "make a difference" / "improve" |
| "deep dive" | "closer look" / "detailed review" |
| "pivot" | "change direction" / "adjust" |
| "align on" | "agree on" / "get on the same page" |
| "unpack" (an idea) | "look at" / "go through" |
| "cadence" | "schedule" / "frequency" |
| "deliverables" | "what we'll provide" / "the work" |
Foreign-isms and Overcorrections
Avoid in written professional comms:
- "Whilst", "amongst" -- use "while", "among"
- "Shall" -- use "will" or "should"
- "Keen" -- use "interested" or "excited about"
- "Brilliant" / "lovely" -- sounds British, use "great" / "sounds good"
- "Dude", "awesome", "totally" in formal emails -- fine on Slack, not in proposals
- Forced casualness -- "Hey buddy!" to a new client is too much
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 slightly 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
Show full SKILL.md (479 more words)Show less
Status update to existing client
Too corporate:
Dear Mr. Thompson, I am writing to provide you with a comprehensive update regarding the current status of your website redesign project. Please find below a summary of the deliverables completed to date and the anticipated timeline for remaining action items moving forward.
Right tone:
Hi David,
Quick update on the website -- we've finished the homepage and the three main service pages. Everything's looking solid.
Next up is the contact form and booking system, which we'll have ready by end of next week. I'll send over a preview link once it's live on the staging site.
Best, [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 favorable response at your earliest convenience.
Right tone:
Hi Sarah,
Thanks for the call 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 hop on a call if you have any questions.
Best, [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 given our current bandwidth constraints.
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.
Best, [Your name]
Context Rules
Corporate clients: Match their formality up one notch but stay clear and human. "Best regards" instead of "Best", but still "Hi [Name]" not "Dear Mr. Smith". Never mirror their jargon back -- if they say "synergize", you say "work together".
Delivering bad news: Be direct but kind. State the issue, explain why briefly, offer the path forward. No filler, no excessive apologies. One "sorry" is enough -- two is apologetic, three is groveling.
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. Use dollar amounts without "USD" unless international context requires it.
Saying no: Respectful and brief. Give the reason (one sentence), offer an alternative if possible. Don't over-explain or apologize excessively.
Following up: Casual but purposeful. "Just checking in on this" is fine. "I trust this email finds you well" is not. "Wanted to bump this to the top of your inbox" works too.
© jezweb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/writing/skills/us-business-english of jezweb/claude-skills.
Open the folder on GitHubat commit 1260fa7
Compare with similar skills
Us Business English next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Us Business English this skilljezweb/claude-skills | 1.1k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Brand Voice Content Creatordavila7/claude-code-templates | 33k | 3 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Voice Buildercharlie947/social-media-skills | 3.8k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Xe Writing StyleXe/x | 337 | — | ~2.2k | Automated safety check: Pass | CC0-1.0 | |
| Agent Styleyzhao062/agent-style | 709 | — | ~1.2k | Automated safety check: Pass | None |
Similar skills
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
Voice Builder
charlie947/social-media-skills
Build a personalised voice profile inside a Codex or Claude project from a short interview plus 3 to 5 sample pieces of writing.
Xe Writing Style
Xe/x
Transform unstructured notes into polished blog posts in Xe Iaso's voice.
Agent Style
yzhao062/agent-style
Literature-backed English technical-prose writing rules. An agent skill from yzhao062/agent-style.
Content Creator
aAAaqwq/AGI-Super-Team
Create SEO-optimized marketing content with consistent brand voice.
More from jezweb/claude-skills
All 52 skills in this repoFavicon Gen
jezweb/claude-skills
Generate custom favicons from logos, text, or brand colours.
Tailwind Theme Builder
jezweb/claude-skills
Set up Tailwind v4 + shadcn/ui themed UI with dark mode. An agent skill from jezweb/claude-skills.
Elevenlabs Agents
jezweb/claude-skills
Build conversational AI voice agents on the ElevenLabs platform.
Responsiveness Check
jezweb/claude-skills
Test website responsiveness across viewport widths using browser automation.
MCP Builder
jezweb/claude-skills
Build MCP servers in Python with FastMCP. An agent skill from jezweb/claude-skills.
GitHub Release
jezweb/claude-skills
Prepare and publish GitHub releases. An agent skill from jezweb/claude-skills.
Related
Categories
Questions about Us Business English
What does Us Business English do?
American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Us Business English is an agent skill from jezweb/claude-skills. American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center).
When should I use Us Business English?
Us Business English fits situations like: the user is writing for an American audience: emails; client communications; any business writing.
How do I install Us Business English in Claude Code?
Run `npx skills add jezweb/claude-skills --skill us-business-english -a claude-code`. Or copy the skill folder (plugins/writing/skills/us-business-english in jezweb/claude-skills) into .claude/skills/us-business-english in your project. Claude Code loads it when a task matches its description.
How do I install Us Business English in Codex?
Run `npx skills add jezweb/claude-skills --skill us-business-english -a codex`. Or copy the skill folder (plugins/writing/skills/us-business-english in jezweb/claude-skills) into .agents/skills/us-business-english in your project. Codex loads it when a task matches its description.
Can I use Us Business English in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jezweb/claude-skills --skill us-business-english -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/us-business-english, .gemini/skills/us-business-english, .github/skills/us-business-english and .opencode/skills/us-business-english in your project.
What does Us Business English need to run?
SKILL.md names no scripts, command-line tools or credentials: Us Business English is instructions for the agent only.
Does Us Business English access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Us Business English safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Us Business English use?
Us Business English is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Us Business English use?
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Us Business English?
Skills that share tags, products or a category with Us Business English: Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars), Brand Voice Content Creator (davila7/claude-code-templates, 33k stars), Voice Builder (charlie947/social-media-skills, 3.8k stars) and Xe Writing Style (Xe/x, 337 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Us Business English?
jezweb (a GitHub user) maintains it in jezweb/claude-skills, which has 1,055 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 9, 2026.
Source: jezweb/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.