Language Coach

Other

Multi-language writing coach for grammar, word choice, collocations, and idiom errors. Supports English, Chinese, Spanish, French, and Japanese. Activated via //en, //cn, //es, //fr, //ja slash commands.

Install

openclaw skills install language-coach

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:

The original sentence/phrase
The corrected version
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