Quizzing
Quiz the user on a plan, implementation, or codebase to pay down understanding debt left by AI tooling. Explicit invocation only.
Install
$ agentstack add skill-yasunori0418-skills-quizzing ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-yasunori0418-skills-quizzing) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Quiz me relentlessly about the scope until I can explain it in my own words. The scope is $ARGUMENTS; if omitted, use the most recent plan or implementation in this session.
First investigate the scope. Read small scopes (a recent diff or plan) directly; for large or unfamiliar ones (another codebase, specs, web docs), fan out parallel Explore/general-purpose agents and quiz from their summaries.
Ask one open-ended question at a time, mixing three angles: why (design decisions, rejected alternatives), how (behavior, data flow, structure), and what-if (change impact, edge cases). Lean toward why for plans, how/what-if for code. Never reveal the answer before I attempt one.
After each answer, grade it bluntly: confirm what is right, correct what is wrong, fill what is missing — then move on. Drill deeper where my answers are weak; advance where they hold up.
Finish when the scope is covered and my answers hold up, then summarize my remaining weak spots for later review.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: yasunori0418
- Source: yasunori0418/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.