quiz-me
Skill0 starsChanged 13 days agoMITView on GitHub
Turn the work the agent just did (or a topic, file, or doc) into a short quiz so the user learns while they ship. Asks 3 to 5 questions one at a time, grades each answer, and explains the gaps. Use when the user says "quiz me", "test me", "did I get this", "check my understanding", or after a large change they must own and maintain.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- marnickvda/pop-quiztheir own version, first seen Nov 8, 2026
- marnickvda/know-it-alltheir own version, first seen Nov 8, 2026
- matthlh/school-3-1their own version, first seen Nov 6, 2026
- seanx10m/skillstheir own version, first seen Nov 1, 2026
- Rayhaan1345/socratic-tutortheir own version, first seen Nov 1, 2026
- jellydn/my-ai-toolstheir own version, first seen Oct 18, 2026
Used with
Projects with it also use reflect and handoff.
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.
Microsoft AzureSkillreflect
Learning capture system that extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes. Use after user corrections ("no", "wrong"), praise ("perfect", "exactly"), or when discovering edge cases. Complements .squad/agents/{agent}/history.md and .squad/decisions.md.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- jellydn/my-ai-tools★ 127same name
- Ciucky/no-numb★ 32same name
- kevmoo/kevmoo_skills★ 22same name
- rodbv/socratic-skills★ 18same name
- Ic3b3rg/learn-skills★ 9same name
- yarikleto/claude-teacher-plugin★ 9same name
- Rayhaan1345/socratic-tutor★ 5same name
- marnickvda/know-it-all★ 3same name
- marnickvda/pop-quiz★ 3same name
- bogdanbaciu21/skills★ 2same name
8 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.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Default: the changes in this session (git diff against the start point, or the files you edited).
- Distinctive: line 31
Wait for the answer before the next question.
- Distinctive: line 38
Do not praise a wrong answer to be kind.
“Common” is measured: kept by at least 6 in 10 of the 18 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.
Files
Quiz me
Goal: the user can maintain what the agent built. Agents write code faster than people read it. A short quiz finds the gaps before they become bugs.
1. Pick the material
- Default: the changes in this session (
git diffagainst the start point, or the files you edited). - Or: the topic, file, or doc the user names.
- Find the 3 to 5 ideas the user must know to own this. Ignore trivia (exact names, line numbers, syntax).
Good targets:
- Why this approach and not the obvious other one.
- What breaks if a key line is removed or changed.
- Where the data comes from and where it goes.
- Which case is not handled.
- How to check that it works.
2. Ask one question at a time
Mix the types:
- Predict: "If the API returns 429, what does
fetchUserdo?" - Spot the bug: show a 3 to 8 line variant with one change. "What is wrong here?"
- Choose: multiple choice with plausible wrong answers. Use the AskUserQuestion tool when you have it.
- Explain back: "In one sentence, why do we cache before we check auth?"
Wait for the answer before the next question. Do not give hints in the question.
3. Grade honestly
- Right: say so in a few words, then add one fact they did not mention.
- Partly right: say which part is right, then fill the gap.
- Wrong: say it is wrong, give the right answer, and point to the exact code (
file:line). - Do not praise a wrong answer to be kind.
4. Score and next step
End with: score (for example 3/5), the one weak area, and one action ("read lib/cache.ts:40-70" or "ask me to explain the retry logic"). Offer a second round on the weak area only.
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
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.