agentleFS
yarikletoyarikleto/claude-teacher-plugin/skills/summary/SKILL.md

summary

Skill9 starsChanged 2 months agoMITView on GitHub

Use when the student is ending a learning session — generates a recap of what was covered, updates knowledge tracking in the global DB, and suggests what to start with next time

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 3 are distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before accessing education data, read ${CLAUDE_PLUGIN_ROOT}/references/education-data.md.

    line 7
  2. Very specific:

    Read <education-db>/dashboard.json for current state

    line 20
  3. Very specific:

    Read relevant <education-db>/topics/*.json for topics covered this session

    line 21
  4. Very specific:

    Read <education-db>/student.json for goals

    line 22
  5. Distinctive:

    Update ALL DB files with session results

    line 24
  6. Very specific:

    Update project-local memory/knowledge_gaps.md if it exists

    line 25
  7. Distinctive:

    Create the file if it doesn't exist

    line 90
  8. Very specific:

    Update status based on session performance

    line 91
  9. Very specific:

    Update depth if student demonstrated deeper understanding

    line 92
  10. Distinctive:

    Add any new misconceptions discovered

    line 94
  11. Very specific:

    Update last_session to today

    line 100
  12. Very specific:

    Update all topic entries with current status/depth/next_review

    line 103
  13. Very specific:

    If you learned new things about the student during this session (e.g., they mentioned a new goal, showed a preference for a different …

    line 122

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Before accessing education data, read ${CLAUDE_PLUGIN_ROOT}/references/education-data.md. Resolve every <education-db> below using that contract. Current session ID: ${CLAUDE_SESSION_ID}.

Session Summary

Generates an end-of-session recap and persists all progress to the global education DB.

Invocation

/claude-teacher:summary — run at the end of a learning session

Process

  1. Review the current conversation — what topics were discussed, quizzed, challenged?
  2. Read <education-db>/dashboard.json for current state
  3. Read relevant <education-db>/topics/*.json for topics covered this session
  4. Read <education-db>/student.json for goals
  5. Generate the summary
  6. Update ALL DB files with session results
  7. Update project-local memory/knowledge_gaps.md if it exists

Summary Format

══════════════════════════════════════════════════
  SESSION SUMMARY — [date]
══════════════════════════════════════════════════

  Duration: [from recorded timestamps, or omit if unknown]
  Project: [current directory]

  LEARNED TODAY
  ─────────────
  ✓ [topic 1] — [one-line what was covered]
  ✓ [topic 2] — [one-line what was covered]
  ~ [topic 3] — [started but not finished]

  QUIZ RESULTS
  ─────────────
  · [topic]: 8/10 (80%) — promoted to solid!
  · [topic]: 5/10 (50%) — stays at learned, review scheduled

  DEPTH CHANGES
  ─────────────
  ↑ [topic]: surface → working (used correctly in challenge)
  ↑ [topic]: working → deep (explained reasoning correctly)

  MISCONCEPTIONS
  ─────────────
  ⚠ [topic]: "[what they said wrong]" — [addressed/still open]
  ✓ [topic]: "[old misconception]" — resolved this session!

  KNOWLEDGE CHANGES
  ─────────────
  ↑ [topic] moved from Weak → Learned
  ↑ [topic] moved from Learned → Solid
  ↓ [topic] — struggled, stays in Weak

  GOAL PROGRESS
  ─────────────
  · Pass OS exam (2026-06-15): 5/10 topics solid (+2 today)

  SPACED REPETITION SCHEDULE
  ─────────────
  Tomorrow: [topic] (review due)
  In 2 days: [topic]
  In 4 days: [topic]

  NEXT SESSION
  ─────────────
  Start with:
    1. Review: [topics due for spaced repetition]
    2. Resolve: [unresolved misconception to address]
    3. Continue: [where we left off]
    4. Next new topic: [what comes next]

══════════════════════════════════════════════════

DB Updates

1. Update/create topic files (<education-db>/topics/<slug>.json)

For each topic covered this session:

  • Create the file if it doesn't exist
  • Update status based on session performance
  • Update depth if student demonstrated deeper understanding
  • Preserve assessment dates and intervals unless a new completed assessment has not yet been saved; apply each assessment once using the shared contract
  • Add any new misconceptions discovered
  • Mark any resolved misconceptions as resolved: true
  • Add session notes

2. Update dashboard (<education-db>/dashboard.json)

  • Update last_session to today
  • Update current_topic
  • Recalculate stats (weak/learned/solid counts)
  • Update all topic entries with current status/depth/next_review

3. Finalize session log (<education-db>/sessions/[date].jsonl)

Append closing entry:

{"time": "[now]", "event": "session_end", "project": "[cwd]", "topics_covered": ["..."], "quizzes_taken": N, "misconceptions_found": N, "misconceptions_resolved": N, "summary": "one-line summary"}

4. Update project-local tracking

Update memory/knowledge_gaps.md:

  • Topics explained → Learned (if new)
  • Topics answered correctly in quiz → promote toward Solid
  • Topics answered incorrectly → Weak
  • Note dates for spaced repetition

5. Update student profile if needed

If you learned new things about the student during this session (e.g., they mentioned a new goal, showed a preference for a different explanation style), update <education-db>/student.json.

Rules

  • Be honest about what was understood vs what needs more work
  • Track mistake patterns, not just topics (e.g., "keeps forgetting to close file descriptors")
  • The "Next Session" section is critical — it's the first thing to check next time
  • Include spaced repetition schedule so the student knows what's coming
  • Show goal progress to maintain motivation
  • Save everything to DB — this is the primary save point for the session

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.