← Back to Skills Marketplace
kaigegao1110

Language Coach

by KaigeGao · GitHub ↗ · v2.0.3 · MIT-0
cross-platform ✓ Security Clean
186
Downloads
0
Stars
1
Active Installs
3
Versions
Install in OpenClaw
/install language-coach
Description
Multi-language writing coach for grammar, word choice, collocations, and idiom errors. Supports English, Chinese, Spanish, French, and Japanese. Activated vi...
README (SKILL.md)

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:

Command Language Example
//en English //en I already send the report
//cn Chinese //cn 我来到了美国已经三年了
//es Spanish //es Yo tengo muchos años de experiencia
//fr French //fr Je suis très bonne en français
//ja Japanese //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
Usage Guidance
This skill is instruction-only and internally consistent with its stated purpose. A few practical things to consider before installing: (1) The SKILL.md asserts user text "never stored or transmitted externally" — that is a developer claim, not a platform enforcement guarantee; if you have strong privacy needs, review the repository locally before installing or avoid sending highly sensitive text. (2) The README shows manual install via GitHub (standard); if you install via an automated tool, inspect what the installer does. (3) Because the skill can be invoked autonomously by agents (platform default), be mindful that it will see any text you prefix with the activation commands. Overall this appears coherent and proportionate for a writing-coach skill.
Capability Analysis
Type: OpenClaw Skill Name: language-coach Version: 2.0.3 The language-coach skill is a legitimate multi-language writing assistant that provides grammar and style corrections via slash commands (//en, //cn, etc.). The skill's logic is defined through clear, non-malicious markdown instructions in SKILL.md and individual command files (e.g., commands/en.md), with no evidence of data exfiltration, unauthorized command execution, or prompt injection attacks. All files align with the stated purpose of providing brief, educational language feedback.
Capability Assessment
Purpose & Capability
Name/description match the provided command files and SKILL.md. All declared pages and command templates are language-correction focused; nothing requests unrelated access (cloud creds, system files, etc.).
Instruction Scope
Runtime instructions restrict behavior to reviewing the user-provided text and returning a single brief correction + one-sentence explanation. The skill does not instruct the agent to read other files, environment variables, or to transmit data to external endpoints.
Install Mechanism
No platform install spec is provided (instruction-only). README offers manual GitHub clone or zip download, which is standard and uses a well-known host (github.com). Nothing downloads from obscure URLs or writes code during automated install.
Credentials
The skill declares no required environment variables, credentials, or config paths. The requested scope (none) is appropriate for a text-correction skill.
Persistence & Privilege
always is false and user-invocable is true (default). The skill does not request elevated system presence or modify other skills. Autonomous invocation remains possible (platform default) but is not flagged by the skill itself.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install language-coach
  3. After installation, invoke the skill by name or use /language-coach
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.3
- Removed tool configuration and related details from SKILL.md. - Simplified documentation by omitting tool usage section and tool input/output examples. - No changes to correction principles, language support, or how the language coach is triggered. - No code or functional changes; documentation update only.
v2.0.2
- Documentation streamlined: removed the "Option 3: Copy from local workspace (this machine)" installation method. - No changes to core features or functionality; adjustments only affect installation instructions in documentation.
v2.0.1
- Improved documentation with detailed error guidance for English, Chinese, Spanish, French, and Japanese. - Added clear correction examples and explanations for each supported language. - Clarified activation method using language-specific commands (//en, //cn, //es, //fr, //ja). - Updated interaction style guidelines to keep corrections brief, friendly, and educational. - Outlined common errors to correct and those to ignore for each language.
Metadata
Slug language-coach
Version 2.0.3
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 3
Frequently Asked Questions

What is Language Coach?

Multi-language writing coach for grammar, word choice, collocations, and idiom errors. Supports English, Chinese, Spanish, French, and Japanese. Activated vi... It is an AI Agent Skill for Claude Code / OpenClaw, with 186 downloads so far.

How do I install Language Coach?

Run "/install language-coach" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Language Coach free?

Yes, Language Coach is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Language Coach support?

Language Coach is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Language Coach?

It is built and maintained by KaigeGao (@kaigegao1110); the current version is v2.0.3.

💬 Comments