fluent-session-analyzer

Parse Fluent session markdown files to extract error patterns and plan adaptive practice sessions.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/xiaoshan1234/ai-skill --skill fluent-session-analyzer-xiaoshan1234
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: fluent-session-analyzer
Source: https://github.com/xiaoshan1234/ai-skill/tree/main/origin/fluent-session-analyzer
Command: npx skills add https://github.com/xiaoshan1234/ai-skill --skill fluent-session-analyzer-xiaoshan1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Language tutors and learners accumulate session reports in markdown files but lack a systematic way to turn those raw records into targeted follow-up practice. This Skill reads recent session files, identifies recurring error patterns, and produces a data-driven plan for the next lesson. ## Core Features & Use Cases - Error Pattern Extraction: Scans session files for correction markers, categorizes errors by type (grammar, vocabulary, prepositions, etc.) and severity, then counts frequency to distinguish typos from critical weaknesses. - Trajectory Tracking: Compares accuracy, error counts, and trends across the last 3-5 sessions to measure progress and tune difficulty. - Session Planning: Generates a structured next-session plan allocating time to top weaknesses, moderate patterns, and integration scenarios. - Use Case: Before starting a Dutch writing lesson, the tutor loads this Skill to review the last three writing session reports, discovers that formal/informal pronoun confusion appeared five times, and builds a 20-minute drill sequence targeting that pattern. ## Quick Start Analyze my last three writing session files in /results and tell me what I should practice next.

Frequently Asked Questions about fluent-session-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze language learning session files to plan the next lesson?β–Ό

Read the 3-5 most recent session markdown files for the relevant skill, count error patterns by category and severity, then allocate session time proportionally: 50% to top critical weaknesses, 30% to moderate patterns, and 20% to an integration scenario.

What file format does the session analyzer expect?β–Ό

It expects markdown files named {skill}-session-{NNN}.md stored in the /results directory, containing correction markers (❌ for errors, βœ… for correct usage), error categories, and severity levels (πŸ”΄ critical, 🟑 moderate, 🟒 minor).

When should I use session markdown analysis instead of the JSON database?β–Ό

Use markdown analysis when you need narrative context like the exact sentence written, the scenario, or feedback received. Use read-db.py on the JSON databases for aggregated counts, trends, and mastery levels instead of re-parsing markdown.

How many past sessions should the analyzer review?β–Ό

Review only the 3-5 most recent session files for the relevant skill. Older data is already consolidated into mistakes-db.json mastery levels, so re-reading the full history adds no value.

How does the analyzer decide which errors to prioritize?β–Ό

Errors appearing once are treated as possible typos and ignored. Patterns occurring 2-3 times are emerging weaknesses worth drilling, while 4 or more occurrences indicate a critical weakness that gets highest priority in the session plan.

Can the session analyzer modify or update session report files?β–Ό

No. Files in /results are immutable records and must never be altered. The Skill is strictly read-only and used only for analysis and planning.