Quiz
Post-work comprehension quiz — after finishing significant work, explain what changed and quiz the user so they stay in the loop and can represent the work in a PR or handoff. This skill should be used when the user says "quiz me", "give me a quiz", "test my understanding", "check whether I understood this", "퀴즈", "내가 이해했는지 확인해줘", or right before creating/merging a PR for work the model largely implemented.From its SKILL.md
npx -y skills add ajitta/know-your-unknowns --skill quizAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.4 KB, as published. Nobody here has run it
Quiz — Post-Work Comprehension Check (Stay in the Loop)
Even delegated work, user must be able to explain the result. Source: Thariq Shihipar — "I like to get it to quiz me about what happened, to make sure I understand what I'm doing and can represent this work when I'm creating a PR or merging it."
Procedure — Part 1: Explain First
Before quiz, explain concisely:
- Overall structure of changes (what created/changed, where)
- Top 3 design decisions and why
- Most likely failure points (if wrong, where does it surface first)
- What user must verify themselves (what model cannot guarantee)
Procedure — Part 2: Quiz
- Ask 5 questions. If AskUserQuestion tool available, use multiple-choice.
- Question priority: incident response ("X dies — where do you look first") > design rationale ("why B, not A") > behavior prediction ("given this input, what result") > rote recall (avoid).
- Grade answers; re-explain only the wrong or blank parts — per "Quiz Me Before I Merge", each wrong answer must point to the exact change site to re-review.
- If IMPLEMENTATION_NOTES.md exists, include at least 1 quiz question on its recorded deviations.
Output Format (HTML Option)
For big pre-merge changes, may build a merge-readiness report as single-file HTML: change summary (per-file collapsible) + quiz UI; wrong answer scrolls to and highlights the relevant change section. No viewer available: fall back to markdown with same structure. Normal cases: in-conversation is enough.
Wrap-Up: Handoff Summary
After quiz, present handoff summary — assume another dev takes over tomorrow:
structure summary / key decisions / how to run & test / incident check order / remaining risks.
If user wants, convert to PR body draft; if work needs reviewer approval,
suggest writing a /unknowns:buy-in doc.