v0.6.0 A skill for Claude Code and other AI agents

Don't read about it.
Predict, try it, then check.

A tutoring skill for any subject. It doesn't explain topics to you. It makes you predict, try it yourself and check, and it keeps a record of what you actually know.

Install
/plugin marketplace add ITZSHOAIB/mastery-tutor

Works with Claude Code, Codex, Cursor, Gemini CLI, Copilot, OpenCode and plain chat.

Step 1 · Predict Playing itself. Tap anything to take over.

You're writing to a colleague who's been ill. Which verb goes in the gap?

Espero que   bien.

How sure are you?

Pick an answer and how sure you are.

Right · Fairly sure

Answer: B, estés. A wish about someone else isn't stated as fact, so the next verb leaves the present.

Logged with your confidence, so it comes back in review.

One module

Every module runs the same loop.

Each stage has its own reference file the agent re-reads before running it, and every check feeds the review log that brings ideas back as warm-ups.

  1. Warm-up

    What's due comes first: ideas from earlier modules, scheduled to return just before you'd forget them.

  2. Spot

    Each module is anchored in something you already do. The tutor starts from your own work.

  3. Probe

    It starts with high-level questions and walks down until it finds the edge of what you know.

  4. Map

    What you hold is marked and skipped. The steps left form a dependency graph to the module's goal.

  5. Steps

    Predict, try, check. At most one prediction and one check per step. A missed check gets repaired before anything builds on it.

  6. Close

    Break it, Plug back and Explain back, graded strictly, then the map redrawn from memory. A module isn't done without all three.

The module map

Your gaps, drawn as a map.

Two to four probing questions find the edge of what you know. What you hold is marked and skipped; the steps left lead to the module's goal, and each one closes only when its check passes.

  1. Probe

    Two answers come back solid. Those ideas are already yours, so they're marked as held.

  2. Map v1

    The steps left are drawn as a dependency graph, ending at the module's goal.

  3. Walk it

    Each step closes only when its check passes. The map shows where you are.

  4. Redraw it

    At the close, before seeing it again, you redraw the map from memory. Each step you miss or misplace is logged for review.

que joins two clauses The present states facts After espero que, estás → estés Why: a wish isn't a fact Requests work the same way Same person: infinitive Goal: wishes about others take the subjunctive
Known before Check passed You're here Still to do

Confidence

Is "Certain" actually right?

Confidence is recorded with every answer, because a confident miss is the most useful thing a question can find. Those are the beliefs that quietly break your work. They're named, traced, repaired and retested later.

The recap page charts how often you're right at each confidence level, and how that's changing. Example numbers below.

Right at each level

Certain: said 95%, right 58%

0%50%100% perfectly calibrated GuessingUnsureFairly sureCertain
100%0% day 0day 60 without review
Illustrative curve. FSRS picks the real dates from your review log.

Spaced review

Back just before you'd forget.

Every check is logged and scheduled with FSRS, so ideas come back just before you'd forget them. Ask "What's due?" or "Quiz me" and earlier modules return as warm-ups.

Grounding

Sourced, not remembered.

A model's memory is stale and unlabelled. Before planning, a separate agent finds the authoritative sources. Before each module, every claim it rests on is checked against them, with a quote and a date. What can't be supported isn't taught as fact, and your own result beats any source.

From a test topic on Python concurrency: claims checked before a module.

Python 3.13 removed the GIL; threads run CPU-bound code in parallel by default
What's New in Python 3.13“experimental support for running in a free-threaded mode”
Contradicted
datetime.utcnow() is the recommended way to get UTC time
datetime docs“Deprecated since version 3.12”
Contradicted
The thread pool's default worker count depends on the CPU count
concurrent.futures docs“min(32, os.cpu_count() + 4)”
Supported
32 workers is a good default for 2,000 HTTP calls
No source found
Unverified

That makes each claim supported, dated and correctable. It doesn't make it infallible.

Any subject

Same loop, any subject.

What changes is the try, the thing you do between predicting and checking. Questions, confidence, misconceptions, spaced review and the module close work the same everywhere.

Predict

Adding one tool to the end of the list keeps every message cached.

You try it

Run cell 2.3 with and without the tool; compare the reused token counts.

Check

The shared run ends inside the tools block. Prediction wrong: the order is one sequence.

Visual pages

Pages it builds, live.

Real outputs of the skill's scripts. Each page is generated from your markdown records and can be thrown away.

Open (opens in a new tab)

The tutor offers a single-purpose page with real measured data, and builds it only if you say yes. It asks the prediction first.

Honest status

Where it is today.

Claude Code is the primary target and the most tested. Elsewhere the install and scripts are tested; a full session there isn't yet, so reports are welcome.

5

Tested

  • Full sessions as a Claude Code plugin
  • Spaced review scheduled with FSRS
  • Your own sources: textbook, notes, past exams
  • Skills CLI install and scripts: Codex, Cursor, Gemini CLI and others
  • Calibration, the module map and the recap page

2

New in 0.6

  • Faded worked examples, redraw the map from memory
  • Grounding: research first, a quoted claim ledger

2

Not yet tested

  • A full session in other coding agents
  • Uploading to claude.ai or Claude desktop
Report how it went

Your first session is one sentence away.

Install it, then ask for what you want to learn. Your records are plain markdown in a folder you own, so switching agents, devices or models loses nothing.

  1. Claude Code
    /plugin marketplace add ITZSHOAIB/mastery-tutor
    /plugin install mastery-tutor@mastery-tutor
  2. Other agents
    npx skills add ITZSHOAIB/mastery-tutor
  3. Anything else

    Copy skills/mastery-tutor/ into your agent's skills folder, or paste SKILL.md into a chat.

I want to read Spanish news without a dictionary by summer.

A few questions first: what do you read now, how much time do you have each week, and do you have any material already?

Then a roadmap of phases and modules, each paired with a try.