Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

us-business-english美国商务英语

Agent Skill

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

总安装

10,419

周安装

443

GitHub Stars

750

下载量

3,650
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

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

简介

us-business-english 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于关键词搜索、任务场景匹配或来源线索梳理等研究检索场景。
  • 通过 npx skills add 命令从 GitHub 仓库安装,需结合原始 README 确认具体用法。
  • 安装前请核实权限范围、维护状态,以及是否涉及联网、命令执行或文件读写操作。
  • 建议在使用时核对来源仓库内容,确保功能与预期一致。

SKILL.md

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)

PatternAmericanNot
-orcolor, favor, honor, behaviorcolour, favour
-izeorganize, realize, specialize, recognizeorganise, realise
-ercenter, fiber, meter, theatercentre, fibre
-enselicense (noun and verb), defense, offenselicence (noun), defence
Single Ltraveling, canceling, modelingtravelling, cancelling
-ogcatalog, dialog, analogcatalogue, dialogue
-mentjudgment, acknowledgmentjudgement, 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.

ContextFormalityGreetingSign-off
Slack/Teams (internal)Casual"Hey" / first nameNone needed
Email to existing clientProfessional friendly"Hi [Name]""Best" / "Thanks"
Email to new clientProfessional"Hi [Name]""Best" / "Thanks"
Proposal or quoteProfessional"Hi [Name]""Best regards" / "Best"
Follow-up after meetingProfessional friendly"Hi [Name]""Thanks" / "Talk soon"
Cold outreachWarm professional"Hi [Name]""Best" / "Thanks"
Formal letter or legalFormal"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:

  1. Best -- default, works almost everywhere
  2. Thanks -- when you're asking for something or appreciating effort
  3. Best regards -- one step more formal, good for proposals
  4. Regards -- neutral, slightly cooler
  5. 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 ofWrite
"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

  1. Lead with the point. First sentence answers the question or states the purpose. Context comes after, not before.
  2. Short paragraphs. Two to three sentences max. One idea per paragraph. White space is your friend.
  3. 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.
  4. Active voice. "We'll send the report Monday" not "The report will be sent on Monday."
  5. Specific over vague. "I'll have this to you by Thursday" not "I'll get back to you soon."
  6. One ask per email. Multiple requests? Number them. Don't bury the second ask in paragraph four.
  7. Match their energy. Short email from client? Short reply. Detailed brief? Detailed response. Don't write five paragraphs when two lines will do.

Examples

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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.52%
按下载量换算1,223

Claude

30.59%
按下载量换算1,117

Cursor

20.55%
按下载量换算750

Gemini CLI

9.78%
按下载量换算357

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills