← ClaudeAtlas

quiz-melisted

Use right after writing or editing code or files for the user — before ending your turn — to quiz them on what was just built and confirm they actually understand it. Also triggers on "quiz me", "test my understanding", "check what I learned", "comprehension check", or recovering the understanding that vaporizes when you orchestrate an agent instead of authoring the code yourself.
sliamh11/Deus · ★ 51 · AI & Automation · score 79
Install: claude install-skill sliamh11/Deus
# /quiz-me — quiz the user on what was just built Adapted from the MIT-licensed no-numb plugin (github.com/Ciucky/no-numb); see `.claude/skills/ATTRIBUTION-no-numb.md`. Runs **host-side**. ## Overview After you write code for someone, they usually understand the result at a high level — what it does, its inputs and outputs — but not the internals or the *why*. That understanding "vaporizes." This skill has you administer a short comprehension quiz on **what you just did this turn**, so the understanding sticks. Being tested is itself the learning (retrieval practice); the quiz is not just a check. **Core principle:** quiz what *this turn* produced, from your own memory of what you just did — not generic trivia, not the whole codebase, not what the app does at a high level. ## When to run - Right after a turn in which you edited or wrote files, before finishing. - When the user runs `/quiz-me`. - When the no-numb Stop hook (`.claude/hooks/nonumb-gate.sh`) blocks your turn and asks you to quiz. (That gate is DEFAULT-OFF; it fires only when the user has opted in via `DEUS_NONUMB` or `~/.config/deus/nonumb.json`.) ## Step 1 — Is it worth quizzing? Look at what you changed this turn. **Bias toward quizzing.** Only skip when the change is *genuinely cosmetic*: formatting / whitespace, a variable rename, a CSS color tweak, a typo fix, a version bump. Everything else → quiz. **When in doubt, quiz.** If you do skip, say so in one line and stop — don't quiz on nothing. ##