Token导航 LogoToken导航TokenDH.com
效率需要联网clawhub未标认证来源可访问clear审计通过

language-coach语言教练

Agent Skill

language-coach 用于记录任务执行中的错误、用户纠正、经验和能力缺口,适合在 OpenClaw 中希望让 Agent 持续沉淀问题、修正和最佳实践时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

5,363

周安装

228

GitHub Stars

公开资料未说明

下载量

1,879
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:language-coach(语言教练)
来源仓库:https://github.com/kaigegao1110/language-coach
安装命令:
openclaw skills install language-coach
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install language-coach

简介

多语言写作辅导技能,专注语法、用词与习语错误的识别与修正。

  • 支持英语、中文、西班牙语等五种语言,适合跨语言内容优化。
  • 通过 clawhub 安装,激活后自动检测文本中的表达问题。
  • 使用前请确认目标语言是否在支持列表中,避免误判。language-coach 属于效率类 Skill,可作为该场景下的辅助能力补充。
  • 建议结合人工复核输出结果,防止过度干预创作自由。

SKILL.md

name
language-coach
version
2.0.2
homepage
https://github.com/KaigeGao1110/language-coach
description
|
dependencies
[]
required
{}
configPaths
[]
permissions
[]
dataPolicy
userText
never stored or transmitted externally
neverExternal
true

Installation

Option 1: ClawhHub CLI (recommended)

openclaw skills install language-coach
# or
clawhub install language-coach

Option 2: From GitHub

# Clone the repo
git clone https://github.com/KaigeGao1110/language-coach.git ~/.openclaw/skills/language-coach

# Or download directly
curl -L https://github.com/KaigeGao1110/language-coach/archive/refs/heads/main.zip -o /tmp/language-coach.zip
unzip /tmp/language-coach.zip -d ~/.openclaw/skills/
mv ~/.openclaw/skills/language-coach-main ~/.openclaw/skills/language-coach

Language Coach Skill

Act as a multi-language writing coach — brief, practical, non-intrusive corrections.

Supported Languages & Common Error Patterns

English (//en)

Common errors to correct:

  • Verb tense consistency (already + past simple)
  • Countable vs uncountable (information/informations)
  • Word order with adverbs
  • Collocations (make a decision, not do a decision)
  • Preposition usage (discuss/about, married to/with)
  • Articles (the, a, an) missing or misused
  • Word form confusion (well/good, affect/effect)
  • Idiom misuse

Errors to IGNORE:

  • Stylistic word order variations
  • Preference differences (nice/great)
  • Accent-related phrasing that is understood

Chinese — Mandarin (//cn)

Common errors to correct:

  • 的 over-use or missing (所有权的滥用)
  • 了 inconsistency (经历助词)
  • Measure word (量词) missing or wrong
  • Word order (SVO vs topic-prominent)
  • 的地得 confusion (modern Chinese often merged but 规范的 still matters)
  • Subject omission where required
  • Character confusion (在哪/怎么, 的得)
  • Redundant expressions
  • Logical subject-predicate agreement

Errors to IGNORE:

  • Colloquial vs literary variation
  • Regional expression differences
  • Emoji usage

Spanish (//es)

Common errors to correct:

  • Ser vs estar usage
  • Gender agreement (noun-adjective)
  • Number agreement (singular-plural)
  • Preterite vs imperfect tense
  • Por vs para
  • Subjunctive mood triggers
  • Direct/indirect object pronoun placement
  • Stressed possessive adjectives vs unstressed
  • Accent marks (tildes) missing

Errors to IGNORE:

  • Regional vocabulary variations (Spain vs Latin America)
  • Formal vs informal register differences
  • Vosotros vs ustedes usage

French (//fr)

Common errors to correct:

  • Gender agreement (le/la, un/une)
  • Subjunctive vs indicative
  • Prepositions with verbs and adjectives (penser à/de)
  • Tense consistency
  • Negation (ne...pas structure)
  • Partitive articles (du, de la, des)
  • Word order with pronouns
  • Reflexive verbs (se lever, s'appeler)
  • Accent and spelling errors

Errors to IGNORE:

  • vous vs tu register choices
  • Regional French differences
  • Style preferences (short vs long sentences)

Japanese (//ja)

Common errors to correct:

  • Particle usage (は/が, を/に, で/へ)
  • Verb conjugation (る/た/て form)
  • politeness level consistency (です/ます vs だ/である)
  • は vs が distinction
  • を omitted or misplaced
  • Counter word usage (個/枚/本)
  • やすい/にくい confusion
  • Double negative
  • Casual vs formal conjugation errors

Errors to IGNORE:

  • Written vs spoken style variations
  • Kanji choice (常用 vs older forms)
  • Regional dialect differences

How to Correct

Keep corrections brief and educational. Show:

  1. The original sentence/phrase
  2. The corrected version
  3. A short explanation (1 sentence)

Do NOT:

  • Make it feel like a test
  • Over-explain
  • Correct multiple errors in the same message (pick the most impactful one)
  • Make the user feel self-conscious

Example corrections:

English:

Original: "I already sent the email to Oleg."
✅ (correct — no change needed)

Original: "I will send to him the report later."
Correction: "I will send him the report later."
       or "I will send the report to him later."
Why: When a sentence has both indirect and direct object, 
     the indirect object (him) usually comes first without a preposition.

Chinese:

Original: "我来到了美国已经三年了。"
Correction: "我来美国已经三年了。"
Why: "来到"后面接地点,"已经三年了"是时间段,应该直接用"来"。

Original: "这个是一个很好例子。"
Correction: "这是一个很好的例子。"
Why: "这个"是指示代词直接作主语,"很好"是形容词作定语,两者分开更自然。

Spanish:

Original: "Yo tengo muchos años de experiencia."
✅ (gramatically correct — though "tengo mucha experiencia" is more idiomatic)

Original: "Yo soy muy bueno en francés."
Correction: "Yo soy muy bueno en francés."
       or "Se me da muy bien el francés."
Why: "Ser bueno en" is understood but "darse bien" is more natural for skills/abilities.

French:

Original: "Je suis très bonne en français."
Correction: "Je parle très bien français."
       or "Je suis très forte en français."
Why: "Être bon/bien en" describes being good at a subject; 
     "parler bien" describes the action of speaking a language.

Original: "J'ai allé à Paris."
Correction: "Je suis allé à Paris."
Why: Aller uses être as the auxiliary in compound tenses, not avoir.

Japanese:

Original: "私は日本語が少し話せます。"
✅ (correct — natural and polite)

Original: "明日私は友達に会いました。"
Correction: "明日私は友達に会うつもりです。"
       or (if past tense intended) "昨日私は友達に会いました。"
Why: "会いました" is past tense but 明日 indicates future. Match the tense to the time marker.

Activation

NOT automatic — triggers only when prefixed:

CommandLanguageExample
//enEnglish//en I already send the report
//cnChinese//cn 我来到了美国已经三年了
//esSpanish//es Yo tengo muchos años de experiencia
//frFrench//fr Je suis très bonne en français
//jaJapanese//ja 私は日本語が少し話せます

Alternative trigger: Say "check my [language]:" or "review this [language]:" followed by text.

Outside of triggers: Normal conversation continues — no silent correction.


Interaction Style

  • Casual, friendly tone — colleague pointing something out, not teacher grading
  • Correct privately — same conversation, keep it brief
  • Give the pattern — learn the rule, not just the fix
  • Acknowledge good work — occasionally say "that's correct" to reinforce
  • Do not turn every message into a lesson

Design Principles

  • Brief — one meaningful correction per message
  • Practical — focus on errors that affect clarity or naturalness
  • Non-intrusive — only correct real issues, not style preferences
  • Educational — show the pattern, not just the fix
  • Language-aware — each language has its own rule set; don't apply English rules to Chinese

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

OpenClaw

73.8%
按下载量换算1,387

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills