uk-business-english▌
jezweb/claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Professional and measured. Polite without being obsequious. Direct without being abrupt. Naturally British without being a caricature. Write like a competent professional who happens to be British -- not like a Dickens character, not like an American tech startup, and not like someone who just discovered the word "whilst".
UK Business English
Professional and measured. Polite without being obsequious. Direct without being abrupt. Naturally British without being a caricature. Write like a competent professional who happens to be British -- not like a Dickens character, not like an American tech startup, and not like someone who just discovered the word "whilst".
Spelling (EN-GB)
| Pattern | British | 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), defense |
| -ise/-ize | Both accepted in GB; prefer -ise for consistency | — |
| Double L | travelling, cancelling, modelling | traveling, canceling |
| -ogue | catalogue, dialogue, analogue | catalog, dialog |
| -ement | judgement, acknowledgement | judgment (legal only) |
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), cheque (payment), grey (not gray).
Date format: Day Month Year, no comma -- 15 January 2026. Abbreviated: 15 Jan 2026. Never Month/Day/Year.
Tone Ladder
Match formality to context. Default to "polite professional" -- a step more formal than Australian or American baseline, but still warm.
| Context | Formality | Greeting | Sign-off |
|---|---|---|---|
| Slack/Teams (internal) | Casual | "Hi" / first name | None needed |
| Email to existing client | Polite professional | "Hi [Name]" | "Kind regards" / "Thanks" |
| Email to new client | Professional | "Dear [Name]" / "Hi [Name]" | "Kind regards" |
| Proposal or quote | Professional | "Dear [Name]" | "Kind regards" / "Yours sincerely" |
| Follow-up after meeting | Polite professional | "Hi [Name]" | "Kind regards" / "Thanks" |
| Cold outreach | Professional | "Dear [Name]" / "Hi [Name]" | "Kind regards" |
| Formal letter or legal | Formal | "Dear [Name]" / "Dear Sir or Madam" | "Yours sincerely" / "Yours faithfully" |
Rule: "Yours sincerely" when you know their name. "Yours faithfully" when you don't (Dear Sir or Madam). Getting this wrong marks you as careless.
Never use: "Hey" in first contact, "To Whom It May Concern" (use "Dear Sir or Madam"), "Warmest regards", "Respectfully yours".
Sign-off Ranking
From most to least common in UK SME context:
- Kind regards -- default, works almost everywhere
- Thanks / Many thanks -- when appreciating effort or asking for something
- Best wishes -- warm, slightly less formal than Kind regards
- Regards -- neutral, slightly cooler
- Yours sincerely -- formal letters, proposals to new clients
Avoid: "Best" on its own (reads as American), "Cheers" in first contact (fine once rapport is established), "Warm regards" (overdone), "Ta" (too informal for anything written).
Avoid List
Americanisms
Replace these reflexively:
| Instead of | Write |
|---|---|
| "reach out" | "get in touch" / "contact" |
| "touch base" | "catch up" / "check in" |
| "circle back" | "come back to" / "follow up" |
| "leverage" (verb) | "use" / "make the most of" |
| "moving forward" | "going forward" / "from here" (or drop it) |
| "actionable insights" | "useful findings" / "what we found" |
| "deep dive" | "closer look" / "detailed review" |
| "bandwidth" (for time) | "time" / "capacity" |
| "gotten" | "got" |
| "could care less" | "couldn't care less" |
| "loop in" | "include" / "copy in" |
| "deliverables" | "what we'll provide" / "the work" |
| "Monday through Friday" | "Monday to Friday" |
| "on the team" | "in the team" |
Forced Britishisms
Avoid in written professional comms:
- "Cheerio", "pip pip", "tally-ho" -- never in professional writing
- "Bloody", "blimey", "crikey" -- spoken register only, and even then sparingly
- Overuse of "rather" and "quite" -- one per email is plenty
- "I dare say" -- sounds like a period drama
- "Awfully good" -- ironic understatement has limits in business writing
- "Old chap", "old boy" -- not this century
Writing Principles
-
Lead with the point. First sentence answers the question or states the purpose. Context comes after, not before. British politeness doesn't mean burying the lead.
-
Short paragraphs. Two to three sentences max. One idea per paragraph. White space is your friend.
-
Measured contractions. "We've", "I'll", "that's" are fine in emails. Use fewer in proposals and formal letters. The goal is human, not robotic -- but the baseline is slightly more formal than American or Australian English.
-
Active voice. "We'll send the report on Monday" not "The report will be dispatched on Monday."
-
Specific over vague. "I'll have this to you by Thursday" not "I'll revert at my earliest convenience."
-
One ask per email. Multiple requests? Number them. Don't bury the second ask in paragraph four.
-
Understate rather than overstate. "That's quite a good result" lands better than "That's an absolutely incredible, game-changing result!" Restraint signals confidence.
Examples
Status update to existing client
Too corporate:
Dear Mr Thompson, I write to apprise you of the current status of your website redesign project. Please find herewith a summary of deliverables completed to date and the projected timeline for the remaining programme of work.
Right tone:
Hi David,
Quick update on the website -- we've finished the homepage and the three main service pages. Coming together nicely.
Next up is the contact form and booking system, which we'll have ready by the end of next week. I'll send through a preview link once it's on the staging site.
Kind regards, [Your name]
Delivering a quote
Too stiff:
Dear Client, Please find enclosed our formal quotation for the proposed scope of works as discussed. We trust this meets with your approval and look forward to receiving your favourable 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. In short: GBP 3,500 for the full site, including the booking system. That covers design, development, and getting it live on your domain.
Happy to arrange a call if you have any questions.
Kind regards, [Your name]
Saying no to a request
Too blunt:
We can't do that.
Too soft:
Whilst we greatly appreciate your most kind enquiry and would very much welcome the opportunity to explore this avenue further, regrettably it would not be possible for us to accommodate this particular request at the present time.
Right tone:
Hi Mark,
Thanks for thinking of us for this. Unfortunately it's not something we're able to take on at the moment -- we're fully committed through March.
If timing works, we'd be happy to look at it in April. Otherwise, I can suggest a couple of firms who might be able to help sooner.
Kind regards, [Your name]
Context Rules
Corporate clients: Match their formality but keep your clarity. "Dear [Name]" and "Yours sincerely" if they use it. Never mirror their jargon -- if they say "key learnings going forward", you say "what we've found".
Delivering bad news: Be direct but considerate. State the issue, explain briefly, offer the path forward. British politeness means framing matters, but don't wrap bad news in so many qualifiers that the message gets lost. One "apologies" is sufficient.
Quoting prices: Clear and confident. "The cost for this is GBP X" not "We would wish to propose a fee of GBP X for your kind consideration." Include what's covered. State VAT position (inclusive/exclusive) explicitly.
Saying no: Polite and brief. "Unfortunately" does the work -- you don't need three sentences of preamble. Give the reason, offer an alternative if possible.
Following up: Purposeful but not pushy. "Just checking in on this" works. "I trust this finds you well" is filler -- drop it. "Wanted to bring this back to the top of your inbox" is fine.
How to use uk-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 uk-business-english
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches uk-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 uk-business-english. Access the skill through slash commands (e.g., /uk-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.6★★★★★27 reviews- ★★★★★Hana Gupta· Dec 16, 2024
I recommend uk-business-english for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Pratham Ware· Dec 12, 2024
uk-business-english reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ava Verma· Nov 7, 2024
Keeps context tight: uk-business-english is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Hana Patel· Oct 26, 2024
uk-business-english is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sakshi Patil· Sep 17, 2024
uk-business-english has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Omar Smith· Sep 1, 2024
uk-business-english has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★James Gill· Aug 20, 2024
Solid pick for teams standardizing on skills: uk-business-english is focused, and the summary matches what you get after install.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Solid pick for teams standardizing on skills: uk-business-english is focused, and the summary matches what you get after install.
- ★★★★★Piyush G· Jul 27, 2024
We added uk-business-english from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Shikha Mishra· Jun 18, 2024
uk-business-english fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 27