tutor-done

Tutor Done

This skill closes an active tutoring topic — the pair to /tutor-start. It calculates the XP earned, marks the topic complete in state.json, runs the two-step feedback flow (thumbs + targeted rotating question), and credits the user with cycles rewards for engaging.

The feedback flow is the load-bearing piece. Per the design decisions doc (D4), feedback is rewarded to fix the "users skip it" problem, with anti-gaming guards (symmetric thumbs reward, substantive-answer guard for the targeted question, daily cycles cap).

---

XP rubric (per-concept)

XP is awarded per concept based on the first_attempt field — the user's first interaction with that concept during the session.

first_attempt	XP awarded	Reasoning
"success"	30	Solved it on the first try. Earned mastery signal.
"needed_hint"	15	Used the hint ladder; learned something but with scaffolding.
"needed_reveal"	5	Needed the canonical answer revealed. Still engaged, still some learning.
null	0	Concept was never attempted (probably skipped during calibration). No XP.

A typical 6-concept topic where the user gets most concepts first-try and needed one hint earns ~150 XP. The numbers are tunable in this rubric — adjust here if the felt-pacing turns out wrong.

---

Step 0 — Resolve the target topic

STATE="$CLAUDE_PLUGIN_ROOT/scripts/state.sh"

0a. Subject resolution

If the user provided an argument (e.g., /tutor-done python-decorators), use that as the slug.

If no argument, find the active topic:

ACTIVE=$(bash "$STATE" get '[.topics | to_entries[] | select(.value.status == "in_progress") | .key]')

If the active list is empty:

"No topic in progress. Run /tutor-status to see what you've started, or /tutor-start <subject> to begin one."

Exit cleanly.

If exactly one in-progress topic, use that slug.

If multiple in-progress topics, ask:

"Multiple topics in progress: [list]. Which one are you closing? (Type the slug, e.g. python-decorators.)"