lang
Skill0 starsChanged 9 months agoMITView on GitHub
Full language coaching review for the current session
1 other project uses a version of this.
Adopted by
Most recently taken up by
- paruff/uFawkesAItheir own version, first seen Oct 22, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- paruff/uFawkesAI★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- language-coachingSkill
- progressSkill
- setupSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 8 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
If the JSON file exists: use it as the source of truth for known patterns
- Very specific: line 22
If the JSON file does NOT exist but the .md file does: read the .md, perform a best-effort migration to create the JSON (see Migration …
- Distinctive: line 23
If neither file exists: proceed without memory context, note this in the review
- Very specific: line 25
Check if a matching pattern exists in the JSON (search by id slug or similar native_form/target_correction)
- Very specific: line 26
If it matches an existing pattern: flag it prominently as recurring, increment times_corrected, update last_seen
- Distinctive: line 27
If it is new: create a new pattern entry in the JSON
- Very specific: line 29
Update last_correct_usage, increment times_correct_since_last_error
- Very specific: line 34
If next_review has passed, flag it as "overdue for review"
- Distinctive: line 35
If reviewed and correct in this session, note the SRS progression
- Very specific: line 37
If the entry has a pronunciation field: display it in the Pronunciation section
- Very specific: line 38
If the entry has NO pronunciation field (pre-v1.3.0 legacy): generate one following the Pronunciation Guidelines from the language-coaching …
- Distinctive: line 40
After the review, write the updated JSON file
- Very specific: line 42
Check if a session entry for today already exists in sessions (from ambient coaching).
- Very specific: line 43
If yes: merge the review data into it.
- Very specific: line 44
If no: create a new entry with: date, project, patterns_addressed, new_patterns, patterns_correct, srs_reviews, vocabulary_taught, notes
- Very specific: line 49
When a .md memory file exists but no .json companion:
- Distinctive: line 51
Read the markdown file
- Very specific: line 65
Create the JSON structure with version: 1
- Distinctive: line 66
Write the JSON file
- Distinctive: line 348
Use the user's native language for explanations when helpful
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Language Coaching — Session Review
Analyze the user's messages in this session and provide detailed language coaching feedback.
Target Language
The target language is: $ARGUMENTS (default to en if empty or not specified).
Instructions
- Review ALL user messages in this conversation
- Reference the user's ACTUAL messages — quote specific phrases
- Read
~/.claude/coaching/{language}-coaching.jsonusing the Read tool- If the JSON file exists: use it as the source of truth for known patterns
- If the JSON file does NOT exist but the
.mdfile does: read the.md, perform a best-effort migration to create the JSON (see Migration Protocol below), then proceed - If neither file exists: proceed without memory context, note this in the review
- For each language issue found in the session:
- Check if a matching pattern exists in the JSON (search by
idslug or similarnative_form/target_correction) - If it matches an existing pattern: flag it prominently as recurring, increment
times_corrected, updatelast_seen - If it is new: create a new pattern entry in the JSON
- Check if a matching pattern exists in the JSON (search by
- For known patterns that the user got RIGHT in this session:
- Update
last_correct_usage, incrementtimes_correct_since_last_error - Progress SRS:
interval_days = ceil(interval_days * ease_factor),next_review = today + interval_days - Mention this in Progress Notes as positive reinforcement
5b. For patterns with active SRS (
next_reviewis not null): - Show the current SRS state in the review: interval, ease_factor, next_review
- If
next_reviewhas passed, flag it as "overdue for review" - If reviewed and correct in this session, note the SRS progression
- Update
- For vocabulary entries reviewed or taught in this session:
- If the entry has a
pronunciationfield: display it in the Pronunciation section - If the entry has NO
pronunciationfield (pre-v1.3.0 legacy): generate one following the Pronunciation Guidelines from thelanguage-coachingskill, update the JSON entry with the new field, and display it
- If the entry has a
- Provide the review in the format below
- After the review, write the updated JSON file
- Regenerate the markdown file from the JSON (follow the Markdown Regeneration format from the language-coaching skill)
- Check if a session entry for today already exists in
sessions(from ambient coaching).- If yes: merge the review data into it. Append any newly discovered patterns to
patterns_addressed, updatenotesto include "Session review performed" - If no: create a new entry with:
date,project,patterns_addressed,new_patterns,patterns_correct,srs_reviews,vocabulary_taught,notes
- If yes: merge the review data into it. Append any newly discovered patterns to
- Recalculate the
statsobject:total_sessions,total_corrections(sum of all patterntimes_corrected),patterns_resolved,patterns_active,vocabulary_size,last_session
Migration Protocol (md-to-json)
When a .md memory file exists but no .json companion:
- Read the markdown file
- Parse each section and extract patterns:
- Under "### Grammar", "### Spelling", etc.: extract each bullet as a pattern
- Under "## False Friends Log": extract as
false_friendtype patterns - Under "## Vocabulary Acquired in Context": extract as vocabulary entries
- Under "## Session History": extract as session entries
- For each extracted pattern, create an entry following the Pattern Object Schema from the
language-coachingskill:- Generate an
idslug as{type}-{kebab-case-2-4-word-description}— NEVER use integer IDs - Set
first_seenandlast_seento today (exact dates not recoverable from freeform markdown) - Set
times_correctedto 1 (minimum, since it was recorded) - Set
resolvedto false - Include ALL required fields:
native_form,target_correction,explanation,examples(array),times_correct_since_last_error: 0,last_correct_usage: null - Include SRS fields:
next_review: null,interval_days: null,ease_factor: null - False friends go in the
patternsarray withtype: "false_friend"— do NOT create a separatefalse_friendskey
- Generate an
- Create the JSON structure with
version: 1 - Write the JSON file
- Regenerate the markdown from JSON (normalizes the format)
- Proceed with the session review as normal
Review Format for English (en)
🇬🇧 English — Session Review
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Grammar Patterns
[List recurring grammar issues with corrections and explanations]
## Vocabulary
[Words used correctly in context — reinforce these]
[Suggest more precise/idiomatic alternatives where applicable]
## Pronunciation
[For vocabulary terms taught this session, show 🔊 native_language approximations]
[Flag pronunciation traps relevant to the user's native_language → English]
## False Friends (native → en)
[Any native language interference patterns detected]
## Idioms & Natural Phrasing
[Suggest more natural ways to express ideas that were technically
correct but sound non-native]
## Spelling
[Typos vs systematic spelling patterns — distinguish between them]
## Progress Notes
[Compare with known patterns from memory file. What improved?
What persists? New patterns discovered?]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Review Format for Spanish (es)
🇪🇸 Español — Session Review
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Grammar Patterns
[Verb conjugation, gender agreement, ser/estar, por/para, subjunctive]
## False Friends (native → es)
[Critical: native-Spanish false cognates detected in context]
## Vocabulary
[Words used correctly — reinforce. Suggest alternatives.]
## Pronunciation
[For vocabulary terms taught this session, show 🔊 native_language approximations]
[Flag pronunciation traps relevant to the user's native_language → Spanish]
## Register & Formality
[tu vs usted, voseo awareness if relevant]
## Progress Notes
[Compare with known patterns from memory file]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Review Format for French (fr)
🇫🇷 Français — Session Review
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Grammar Patterns
[Articles & gender, partitive, verb conjugation, subjunctive triggers]
## Gender
[Noun gender errors, adjective agreement — le/la confusion]
## False Friends (native → fr)
[Native-French false cognates detected in context]
[Critical for pt-BR: attendre/atender, entretenir/entreter, assister/assistir]
## Vocabulary
[Words used correctly — reinforce. Suggest alternatives.]
## Pronunciation
[For vocabulary terms taught this session, show 🔊 native_language approximations]
[Flag: liaison rules, nasal vowels, silent final consonants]
## Prepositions
[à/de/en/dans patterns, country prepositions (en/au/aux)]
## Progress Notes
[Compare with known patterns from memory file]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Review Format for Italian (it)
🇮🇹 Italiano — Session Review
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Grammar Patterns
[Articles (il/lo/la/i/gli/le), auxiliary choice (essere vs avere), verb conjugation]
## Spelling & Double Consonants
[Double consonant errors — critical in Italian: anno/ano, penna/pena]
[Accent placement: è vs é]
## False Friends (native → it)
[Native-Italian false cognates detected in context]
[CRITICAL for pt-BR: extremely high mutual intelligibility = frequent traps]
[e.g., esperto, caldo, burro, camera, guardare, salire]
## Vocabulary
[Words used correctly — reinforce. Suggest alternatives.]
## Pronunciation
[For vocabulary terms taught this session, show 🔊 native_language approximations]
[Flag: double consonant length, open/closed vowels, gl/gn sounds]
## Verb Conjugation
[Passato prossimo vs imperfetto, congiuntivo, irregular verbs]
## Progress Notes
[Compare with known patterns from memory file]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Review Format for German (de)
🇩🇪 Deutsch — Session Review
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Grammar Patterns
[Verb position (V2 rule, subordinate clause verb-final), modal verbs, separable prefixes]
## Cases
[Nominativ/Akkusativ/Dativ/Genitiv errors, preposition + case requirements]
[Two-way prepositions: in, an, auf, über, unter, vor, hinter, neben, zwischen]
## Gender & Articles
[der/die/das errors, article declension across cases]
[Compound noun gender (follows last component)]
## False Friends (native → de)
[Native-German false cognates detected in context]
[e.g., en "gift" ≠ de "Gift" (poison), en "become" ≠ de "bekommen" (receive)]
## Vocabulary
[Words used correctly — reinforce. Suggest alternatives.]
## Pronunciation
[For vocabulary terms taught this session, show 🔊 native_language approximations]
[Flag: ch sounds, Umlauts, final devoicing, word stress in compounds]
## Word Order
[V2 violations, subordinate clause verb position, TeKaMoLo]
## Progress Notes
[Compare with known patterns from memory file]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Review Format for Japanese (ja)
🇯🇵 日本語 — Session Review
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Grammar Patterns
[Particle usage, verb conjugation, sentence structure (SOV)]
## Particles
[は/が, に/で, を/が with potential verbs, compound particles]
## Keigo (Honorifics)
[丁寧語/尊敬語/謙譲語 usage, appropriate register for context]
## False Friends
[和製英語 (wasei-eigo) that differ from actual English/native language usage]
[e.g., マンション = apartment, サービス = free/complimentary]
## Vocabulary
[Words used correctly — reinforce. Suggest alternatives.]
## Pronunciation
[For vocabulary terms taught this session, show 🔊 native_language approximations]
[Flag: pitch accent, long vowels, geminate consonants (っ)]
## Writing System
[Kanji readings, hiragana/katakana usage, common kanji errors]
## Progress Notes
[Compare with known patterns from memory file]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Review Format for Korean (ko)
🇰🇷 한국어 — Session Review
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Grammar Patterns
[Particle usage, verb conjugation, sentence structure (SOV), connective endings]
## Particles
[은/는 vs 이/가, 에 vs 에서, object marker 을/를]
## Honorifics
[Speech levels (합쇼체/해요체/해체), -(으)시- infix, special honorific vocabulary]
## False Friends
[Konglish (콩글리시) terms that differ from English]
[Sino-Korean words with different usage than Japanese/Chinese cognates]
## Vocabulary
[Words used correctly — reinforce. Suggest alternatives.]
## Pronunciation
[For vocabulary terms taught this session, show 🔊 native_language approximations]
[Flag: consonant sound changes, 받침 rules, vowel distinctions]
## Hangul Spelling
[받침 errors, sound change rules (nasalization, palatalization), common traps]
## Progress Notes
[Compare with known patterns from memory file]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Review Format for Dutch (nl)
🇳🇱 Nederlands — Session Review
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Grammar Patterns
[V2 rule violations, separable verb errors, er-constructions, modal verb placement]
## de/het (Gender)
[de/het errors, adjective inflection (de grote man vs het grote huis vs een groot huis)]
[Diminutive gender (always het)]
## Spelling
[dt-rule errors (hij vindt, jij wordt), open/closed syllable rules]
[ei/ij confusion, double vowel patterns]
## False Friends (native → nl)
[Native-Dutch false cognates detected in context]
[e.g., en "slim" ≠ nl "slim" (smart), en "monster" ≠ nl "monster" (sample)]
[e.g., de "eventueel" = possibly (not eventually)]
## Vocabulary
[Words used correctly — reinforce. Suggest alternatives.]
## Pronunciation
[For vocabulary terms taught this session, show 🔊 native_language approximations]
[Flag: g/ch guttural sounds, ui/eu/oe diphthongs, schwa rhythm]
## Word Order
[V2 violations, subordinate clause verb position, inversion after adverbs]
## Diminutives
[Suffix selection (-je/-tje/-pje/-etje/-kje), meaning shifts, gender (always het)]
## Progress Notes
[Compare with known patterns from memory file]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━For All Languages (all)
Provide a combined review covering all active languages from the session. Separate each language into its own section.
Important
- Explain the WHY behind corrections, not just the fix
- Prioritize patterns over one-off typos
- Be encouraging about correct usage, not just corrective
- Use the user's native language for explanations when helpful
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

