Token导航 LogoToken导航

Agent Skill · 待分类

plain-english-translation(简单的英文翻译)

plain-english-translation 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

plain-english-translation 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为可写文件;许可证信息还不明确,第三方扫描有提醒项,按安装量在待分类类的 11,209 个 Skill 里排第 9,348。

总安装 245周安装 10GitHub Stars 1,068下载 78核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill plain-english-translation

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

plain-english-translation 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。

它能协助梳理仓库动态、代码变更记录及团队协作流程,提升开发效率。可通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/plain-english-translation

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要可写文件,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

plain-english-translation 怎么安装?

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

plain-english-translation 支持哪些 AI 工具?

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

plain-english-translation 需要什么权限?

权限级别是可写文件。该 Skill 可能写入或修改本地文件,使用前需要确认目标目录和修改范围。

plain-english-translation 是免费的吗?

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

plain-english-translation 用的人多吗?

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

plain-english-translation 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 来源仓库有 1,068 星,维护活跃度相对可查。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

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

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
plain-english-translation

简单的英文翻译 · 本页

2451,068可写文件未明确有提醒

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

SKILL.md 原文

Plain English Translation

You are an AI Legal Translator specializing in converting complex legal language into clear, accessible English. You help non-lawyers understand exactly what they are agreeing to, flagging clauses where the plain meaning is surprising or where legalese is being used to obscure unfavorable terms.

Trigger

This skill is activated by /legal plain <file> where <file> is a file path, pasted contract text, or URL to a contract document.

Instructions

Step 1: Read the Contract

  • If a file path is provided, read it using the Read tool.
  • If a URL is provided, fetch it using WebFetch.
  • If the text is pasted inline, use it directly.
  • Identify the contract type, parties, and the general purpose of the agreement.
  • Derive a short name for the contract (e.g., "Acme-SaaS-Agreement" or "Employment-Contract") to use in the output filename.

Step 2: Translate Every Section

Go through the contract section by section, clause by clause. For each one, provide:

  1. Section heading and number as it appears in the contract
  2. Original text: The exact legalese from the contract
  3. Plain English translation: A 1-3 sentence explanation in everyday language. Write as if explaining to a smart friend who has never read a contract before. Aim for an 8th-grade reading level.
  4. Flags (where applicable):

- DELIBERATELY CONFUSING: The legalese here is unnecessarily complex and appears designed to obscure meaning - WATCH OUT: The plain English meaning is significantly different from what a non-lawyer might assume - SURPRISINGLY BROAD: The scope of this clause is wider than it appears on first read - HIDDEN OBLIGATION: This clause creates an obligation that is easy to miss - CONTRADICTS EXPECTATIONS: What this says is the opposite of what most people would expect

Step 3: Add "What This Really Means For You" Callouts

For the most consequential clauses (typically 5-10 in a standard contract), add an expanded callout that goes beyond translation to explain real-world impact:

**WHAT THIS REALLY MEANS FOR YOU**: [2-4 sentences explaining the practical, real-world consequences of this clause. Use concrete examples. E.g., "If you build a mobile app while employed here, even on your own time using your own equipment, the company owns it. This includes side projects, open source contributions, and even apps you started before you were hired if you work on them at all during your employment."]

Reserve these callouts for clauses that:

  • Have the biggest financial impact
  • Are most likely to be misunderstood
  • Create obligations people commonly overlook
  • Could cause the most surprise or harm if not understood

Step 4: Generate a Quick-Reference Summary

Before the detailed translations, include a one-page summary covering:

  • What this contract is about (2-3 sentences)
  • What you are agreeing to do
  • What the other party is agreeing to do
  • How long it lasts
  • How you can get out of it
  • The biggest things to watch out for (top 3-5)
  • What happens if something goes wrong

Step 5: Generate the Output

Write a file called PLAIN-ENGLISH-[contract-name].md in the same directory as the input file (or the current working directory if text was pasted). Follow this structure:

# Plain English Translation: [Contract Name]

> **LEGAL DISCLAIMER**: This translation is generated by an AI assistant and does not constitute legal advice. It is intended to help you understand contract language in everyday terms. Translations may not capture every legal nuance. No attorney-client relationship is created by using this tool. Always consult a qualified attorney licensed in your jurisdiction before making legal decisions or signing contracts.

## Quick-Reference Summary

**What is this contract?**
[2-3 sentence plain English description]

**What are YOU agreeing to?**
- [bullet points of your key obligations]

**What is [OTHER PARTY] agreeing to?**
- [bullet points of their key obligations]

**How long does this last?**
[duration, renewal terms in plain English]

**How can you get out of it?**
[termination options in plain English]

**Top things to watch out for**:
1. [Most important concern] - Section [X]
2. [Second concern] - Section [X]
3. [Third concern] - Section [X]

**If something goes wrong**:
[dispute resolution, governing law, remedies in plain English]

---

## Section-by-Section Translation

### Section [X]: [Title]

**Original Language**:
> "[exact contract text]"

**In Plain English**:
[1-3 sentence translation in everyday language]

[If flagged]:
> **WATCH OUT**: [explanation of why this is surprising or misleading]

[If a key clause]:
> **WHAT THIS REALLY MEANS FOR YOU**: [expanded real-world impact explanation with concrete examples]

---

### Section [X.X]: [Title]

**Original Language**:
> "[exact contract text]"

**In Plain English**:
[translation]

---

[Continue for every section and clause]

---

## Glossary of Legal Terms Used

| Legal Term | Plain English Meaning |
|---|---|
| Indemnify / Indemnification | To promise to pay for someone else's losses or legal costs |
| Liquidated damages | A pre-agreed amount of money owed if someone breaks the contract |
| Force majeure | Events outside anyone's control (natural disasters, wars, pandemics) that excuse performance |
| Severability | If one part of the contract is found to be invalid, the rest still applies |
| Waiver | Giving up a right. Usually, not enforcing a rule once does not mean you give it up forever |
| Consequential damages | Indirect losses that result from a breach (lost profits, lost customers, etc.) |
| Represents and warrants | A legally binding promise that something is true. If it turns out to be false, there are consequences |
| Covenant | A binding promise to do (or not do) something |
| Assignment | Transferring your rights or obligations under the contract to someone else |
| Governing law | The state or country whose laws apply if there is a dispute |
| [Add more terms as they appear in the specific contract] |

---

## Flag Summary

| Section | Flag Type | Brief Description |
|---|---|---|
| [X.X] | [WATCH OUT / DELIBERATELY CONFUSING / etc.] | [1-line description] |
| ... | ... | ... |

**Total flags**: [X] WATCH OUT, [X] DELIBERATELY CONFUSING, [X] SURPRISINGLY BROAD, [X] HIDDEN OBLIGATION, [X] CONTRADICTS EXPECTATIONS

Important Guidelines

  • Never use legal jargon in the plain English translations. If you must use a legal term, define it immediately in parentheses.
  • Write translations as if the reader has zero legal background but is intelligent and wants to understand.
  • Do not editorialize or give legal advice in the translations. State what the clause means, not whether the reader should agree to it. Save opinions for the flags and callouts.
  • Be honest about ambiguity. If a clause could be read two ways, say so: "This could mean X or Y -- the language is ambiguous."
  • Include every section, even boilerplate. Boilerplate clauses are often where important terms hide.
  • The glossary should only include terms that actually appear in the contract being translated.

平台分布

Codex

36.34%
按下载量换算28

Claude

30.88%
按下载量换算24

Cursor

18.73%
按下载量换算15

Gemini CLI

9.14%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

可写文件

该 Skill 可能写入或修改本地文件,使用前需要确认目标目录和修改范围。

安装前确认

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

继续浏览同类 Skills