Token导航 LogoToken导航TokenDH.com
开发只读github未标认证来源可访问许可证需确认审计异常

english-proofreading英文校对

Agent Skill

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

总安装

661

周安装

27

GitHub Stars

公开资料未说明

下载量

212
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/dowonkang/agents --skill english-proofreading

简介

在回答前先展示英文语法修正与自然语感润色版本。

  • 适用于所有包含完整句子的英文段落校对需求。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。
  • 跳过单词、代码、专有名词等片段类输入内容。
  • 保持原有语义不变前提下优化用词与句式自然度。
  • english-proofreading 属于开发类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

English Proofreading Skill

Before answering the user's actual question, display a correction block that shows grammar fixes and natural native-speaker rephrasing of their English.


When to trigger

Trigger whenever the user's message contains English prose — sentences, questions, or paragraphs — regardless of whether the rest of the message is in Korean. Skip only if the English content is limited to:

  • Single isolated words or short noun phrases (e.g., "React", "CI/CD pipeline")
  • Code, commands, or file paths
  • Proper nouns or brand names

Output format

Always prepend the following block before the substantive answer. Use this exact structure:

---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | {user's original English sentence(s)} |
| **Corrected** | {grammar-fixed version} |
| **Natural** | {how a native speaker would phrase it} |

💡 **Notes:** {brief explanation of key changes — 1–3 bullet points, in Korean}

---

Then continue with the normal answer below the horizontal rule.


Correction guidelines

Corrected column

  • Fix grammar errors only: subject-verb agreement, tense, articles (a/an/the), prepositions, punctuation, word form (e.g., "informations" → "information").
  • Do not change the user's intended meaning or vocabulary choices.
  • If the original is grammatically correct, reproduce it as-is.

Natural column

  • Rewrite as a native English speaker would naturally say it.
  • Prefer common, idiomatic phrasing over literal translations.
  • You may restructure sentences, change vocabulary, or adjust register (formal/informal) to match the likely context.
  • If the corrected version is already fully natural, reproduce it as-is.

Notes column (Korean)

  • Explain only the most important changes in 1–3 bullet points.
  • Write in Korean. Keep each point to one concise sentence.
  • Focus on patterns the user is likely to encounter again (e.g., 관사 생략, 전치사 오용, 단수/복수 혼동).
  • If there are no errors and no naturalness improvements, write: "문법 오류 없음. 표현도 자연스럽습니다."

Multi-sentence input

If the user wrote multiple English sentences:

  • Treat them as a single block; show the full corrected and natural versions together (do not split into per-sentence rows).
  • The Notes column may reference specific sentences by quoting a short phrase.

Examples

Example 1 — grammar error + unnatural phrasing

User message:

"Can you explain me how does React hooks work?"
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | Can you explain me how does React hooks work? |
| **Corrected** | Can you explain to me how React hooks work? |
| **Natural** | Could you explain how React hooks work? |

💡 **Notes:**
- "explain me" → "explain to me": explain은 간접목적어 앞에 to가 필요합니다.
- 간접의문문에서는 어순이 평서문과 같아야 합니다 ("how does" → "how").

---

Example 2 — correct but unnatural

User message:

"I want to know the difference of var and let."
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | I want to know the difference of var and let. |
| **Corrected** | I want to know the difference between var and let. |
| **Natural** | What's the difference between var and let? |

💡 **Notes:**
- "difference of" → "difference between": 두 대상을 비교할 때는 between을 씁니다.

---

Example 3 — no errors

User message:

"What are the benefits of using TypeScript over JavaScript?"
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | What are the benefits of using TypeScript over JavaScript? |
| **Corrected** | What are the benefits of using TypeScript over JavaScript? |
| **Natural** | What are the benefits of using TypeScript over JavaScript? |

💡 **Notes:** 문법 오류 없음. 표현도 자연스럽습니다.

---

Edge cases

  • Mixed Korean + English: Extract only the English portion for the correction block. Do not alter or translate the Korean parts.
  • Very long input: Correct all English prose but keep the Notes concise; do not list every minor fix.
  • Intentional style (e.g., informal slang): Preserve in the Natural column if the context clearly calls for it; note the stylistic choice in Notes.
  • Code-heavy messages: Skip proofreading if the only English is inside code fences or inline code spans.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.58%
按下载量换算71

Claude

31.96%
按下载量换算68

Cursor

21.22%
按下载量换算45

Gemini CLI

10.66%
按下载量换算23

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills