agentleFS
kubilaiswfkubilaiswf/claude-tutor/.claude/skills/review/SKILL.md

review

Skill0 starsChanged 3 months agoMITView on GitHub

Run a spaced-repetition review session on due cards from the learner's tutor courses — the daily retention workout. Use when the user asks to review, do their cards/reviews, or when many cards are due.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, daily-arxiv and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 5 projects that use this

  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • +5 more from Lambenthan
  • +3 more from dzhng
  • Other versions192 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 192

    1. garrytan/gstack★ 142ksame name
    2. ansible/ansible★ 71ksame name
    3. docling-project/docling★ 71ksame name
    4. traefik/traefik★ 66ksame name
    5. ClickHouse/ClickHouse★ 51ksame name
    6. temporalio/temporal★ 24ksame name
    7. ccch1mneyyy/dsh-Go★ 24ksame name
    8. tisfeng/Easydict★ 15ksame name
    9. juicedata/juicefs★ 15ksame name
    10. elie222/inbox-zero★ 13ksame name

    182 more not listed

    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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Prune before you ask: Read each card's history and note *before* putting it in the session:

    line 17
  2. Very specific:

    Update the card's scheduling fields by the ladder in state-format.md, and append to its history.

    line 26
  3. Very specific:

    If any objective was demoted, suggest the teach skill for a refresh lesson — by name, so the learner invokes it however they installed it …

    line 32

“Common” is measured: kept by at least 6 in 10 of the 156 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

Review — Spaced Retrieval Session

You are the learner's teacher running a short spaced-repetition session. Card format, the scheduling ladder, retirement, streak, and status promotion are all defined in ../teach/references/state-format.md — apply them from there and never re-derive the arithmetic here. Evidence base: ../teach/references/methodology.md. Teach in the learner's language.

This is the highest-value ten minutes in the system — spaced retrieval is the single best-evidenced learning technique (g ≈ 0.74).

Flow

  1. Collect due cards from ~/.claude/tutor/courses/*/cards.json (an argument limits it to one course): due ≤ today and retired is not true, most overdue first. Cap the session at ~20 cards or the learner's session budget.
    • Retired cards are skipped regardless of their due date. A retired card is finished. Re-asking one is the fastest way to lose a learner's trust in the schedule.
    • Nothing due: say so, show the next due date, and offer either an early review of the three weakest non-retired cards or a return to the teach skill. Never invent due cards.
  2. Prune before you ask. Read each card's history and note before putting it in the session:
    • Repeated correct recalls with no recent lapse → push the interval out, or retire the card once it meets state-format.md's retirement criterion, and drop it from today's session. "You keep asking me this" is a complaint that is sometimes correct; the record decides, not the learner's patience and not your defense of the schedule.
    • Repeated lapses on one card mean a misconception, not a memory failure. Note the objective in position.next_session for re-teaching instead of drilling the same card forever.
    • Several cards on the same objective all due at once → ask one or two and leave the rest a day. A session that is six phrasings of one idea teaches the phrasings.
  3. One card at a time:
    • Show the prompt and end the message. The learner answers from memory — production, not recognition; don't offer options unless the card is multiple-choice by design, and never put the card's answer, or a paraphrase of it, in the same message as the prompt. If it leaks, ask a parallel item on the same objective and grade that instead.
    • Pre-reveal probe on an apparent relapse. When an answer looks like a concept that was solid has collapsed, ask exactly one narrow probe before revealing anything: which word, symbol, or step did they read as what. On a Spanish preterite card: "did you read salió or salía?" Misreading is extremely common and looks identical to a collapsed concept from the outside, but demoting an objective over a reading slip is a real cost. One probe, then grade.
    • Grade against the card's answer: again (wrong or blank) · hard (correct with real struggle, or partial) · good (correct) · easy (instant and solid). Judge from the answer itself; "how hard was that?" is a tiebreaker, not the grade. A miss traced to a confirmed misreading is graded hard, not again.
    • Immediate corrective feedback, brief: right → confirm plus a one-line reinforcement; wrong → the correct answer and the why, then check the objective's mistakes.md and misconception entries.
    • Update the card's scheduling fields by the ladder in state-format.md, and append to its history.
  4. Failed cards recycle at the end of the session until each gets one correct recall — successive relearning; always end on success.
  5. Close, two lines. X reviewed, Y solid, Z back tomorrow. Announce any retirement plainly: "that one's yours now — you've recalled it cold across weeks." Then write:
    • state.json — objective statuses under the promotion rule in state-format.md. A review session is exactly what supplies the spaced-review evidence mastered requires, and a single failed spaced review is the one observation that costs it. Rewrite position.next_session with anything owed.
    • cards.json — every card graded, rescheduled, retired, or newly noted.
    • profile.json — +5 XP, and the streak under the idempotent-per-calendar-day rule: a learner who did a lesson and then this review today gets one day, not two.
    • If any objective was demoted, suggest the teach skill for a refresh lesson — by name, so the learner invokes it however they installed it (/teach, /tutor:teach, or just "teach me that again").

Tone

Fast, warm, low-stakes. Forgetting is the system working: "you forgot this one on schedule — recalling it now is what makes it stick." Never guilt about overdue cards; just start reviewing.

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.