agentsclimarketplace

Change quiz

Skill MaybeMonad/skills/skills/unknown-reduction/change-quiz

Install
npx -y skills add MaybeMonad/skills --skill change-quiz

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 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.

What its author says it does

Copied from the file, not written here

Post-implementation learning and quiz workflow for making the user understand a code change before merge, release, review, or handoff. Use when the user asks for a quiz, wants to understand what changed, says merge only when I pass, or needs a report with context, intuition, behavior, risks, and verification followed by comprehension questions.

SKILL.md

1.8 KB, as published. Nobody here has run it

Change Quiz

Use this skill when the user wants to understand a completed change deeply enough to review, merge, or hand it off. The quiz should test behavior and risk, not trivia.

Workflow

  1. Inspect the actual change:
    • Diff, touched files, tests, runtime checks, implementation notes, and relevant existing code paths.
  2. Explain the change:
    • Problem, previous behavior, new behavior, important files, data flow, edge cases, validation, and residual risk.
  3. Build intuition:
    • Explain why the implementation works in the local architecture.
    • Call out non-obvious dependencies and failure modes.
  4. Create the quiz:
    • Ask 5-10 questions depending on change size.
    • Prioritize behavior, tradeoffs, risk, and validation.
    • Include scenario questions, not just recall questions.
  5. Hold the answer key unless the user asks for a self-study version.
  6. Grade the user's answers against the behavior that actually shipped.

Report Shape

  1. Context.
  2. What changed.
  3. How it works.
  4. Files and code paths.
  5. Verification.
  6. Residual risks.
  7. Quiz.

Rules

  • Do not quiz on filenames unless the path matters to understanding behavior.
  • Do not claim the user passed unless their answer covers the real risks.
  • If verification is incomplete, include that in both the report and quiz.
  • If the user fails, explain the gap and ask a follow-up question on that gap.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.