Token导航 LogoToken导航

Agent Skill · 研究检索

uk-business-english(英国商务英语)

uk-business-english 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

uk-business-english 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 11,845。

总安装 10,833周安装 434GitHub Stars 750下载 3,507核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:uk-business-english(英国商务英语)
来源仓库:https://github.com/jezweb/claude-skills
仓库路径:skills/uk-business-english
安装命令:
npx skills add https://github.com/jezweb/claude-skills --skill uk-business-english
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jezweb/claude-skills --skill uk-business-english

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找和筛选信息,适合根据关键词快速定位候选结果。可在多种宿主环境中使用,支持任务场景导向的检索。安装命令:npx skills add https://github.com/jezweb/claude-skills --skill uk-business-english。建议确认来源线索和权限范围,避免越界访问。

注意维护状态及是否依赖外部服务调用。

来源仓库内路径:skills/uk-business-english

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jezweb/claude-skills --skill uk-business-engli…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

uk-business-english 怎么安装?

在终端执行 npx skills add https://github.com/jezweb/claude-skills --skill uk-business-english。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

uk-business-english 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

uk-business-english 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

uk-business-english 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

uk-business-english 用的人多吗?

公开数据是累计安装 10,833 次,近一周安装 434 次,下载 3,507 次,GitHub 750 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

uk-business-english 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
uk-business-english

英国商务英语 · 本页

10,833750只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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)

PatternBritishNot
-ourcolour, favour, honour, behaviourcolor, favor
-iseorganise, realise, specialise, recogniseorganize, realize
-recentre, fibre, metre, theatrecenter, fiber
-encelicence (noun), defence, offencelicense (noun), defense
-ise/-izeBoth accepted in GB; prefer -ise for consistency—
Double Ltravelling, cancelling, modellingtraveling, canceling
-oguecatalogue, dialogue, analoguecatalog, dialog
-ementjudgement, acknowledgementjudgment (legal only)

Noun/verb splits:

NounVerb
licencelicense
practicepractise
adviceadvise

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.

ContextFormalityGreetingSign-off
Slack/Teams (internal)Casual"Hi" / first nameNone needed
Email to existing clientPolite professional"Hi [Name]""Kind regards" / "Thanks"
Email to new clientProfessional"Dear [Name]" / "Hi [Name]""Kind regards"
Proposal or quoteProfessional"Dear [Name]""Kind regards" / "Yours sincerely"
Follow-up after meetingPolite professional"Hi [Name]""Kind regards" / "Thanks"
Cold outreachProfessional"Dear [Name]" / "Hi [Name]""Kind regards"
Formal letter or legalFormal"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:

  1. Kind regards -- default, works almost everywhere
  2. Thanks / Many thanks -- when appreciating effort or asking for something
  3. Best wishes -- warm, slightly less formal than Kind regards
  4. Regards -- neutral, slightly cooler
  5. 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 ofWrite
"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

  1. 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.
  2. Short paragraphs. Two to three sentences max. One idea per paragraph. White space is your friend.
  3. 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.
  4. Active voice. "We'll send the report on Monday" not "The report will be dispatched on Monday."
  5. Specific over vague. "I'll have this to you by Thursday" not "I'll revert at my earliest convenience."
  6. One ask per email. Multiple requests? Number them. Don't bury the second ask in paragraph four.
  7. 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.

平台分布

Codex

33.84%
按下载量换算1,187

Claude

30.43%
按下载量换算1,067

Cursor

19.49%
按下载量换算684

Gemini CLI

10.54%
按下载量换算370

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills