Content
77%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, highly actionable instruction skill: a numbered protocol with explicit recap-confirmation checkpoints, feedback loops for mid-interview recovery, BAD/GOOD examples, and clean one-level-deep references to real files. The main weaknesses are moderate redundancy (the one-question rule and mindset material repeated across sections) and a pseudo-executable 'Quick diagnostic' bash snippet that reads as runnable but is not.
Suggestions
Remove or rewrite the 'Quick diagnostic' section — 'echo "$USER_PROMPT" | head -c 200' is not executable ($USER_PROMPT undefined) and its comment falsely claims the command 'Returns interview or answer-directly'; replace with a one-line prose heuristic or delete it.
Trim redundancy: the one-question-per-turn rule appears in Protocol step 2, NEVER rule #1, and Verification; consolidate or cut the 'Mindset' section, which restates the intro rather than instructing.
Consider moving the six NEVER rules with WHY/BAD/GOOD detail into a reference file (alongside question-design.md) to reduce main-file token load, keeping only the rule headlines inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient, but includes unnecessary material: the 'Mindset' section is explanatory rather than instructional ('The interview is not a checklist to complete — it is a chain of decisions'), the opening paragraph restates the description, the one-question rule is stated three times (Protocol step 2, NEVER rule #1, and Verification), and the 'Quick diagnostic' bash block adds little. Matches the level-3 anchor of mostly efficient with some unnecessary explanation; not level 4 given the number of trims available. | 3 / 5 |
Actionability | For an instruction-only skill the guidance is highly actionable: a numbered 7-step protocol, concrete tool direction ('Use the AskUserQuestion tool for a single question at a time'), literal example opening text, BAD/GOOD contrast pairs, and a troubleshooting table. Minor gap: the 'echo "$USER_PROMPT" | head -c 200' block is presented as a runnable diagnostic but is not executable as written, and its comment claiming it 'Returns interview or answer-directly' is inaccurate. Matches level 4, not level 5, due to that pseudo-executable snippet. | 4 / 5 |
Workflow Clarity | The protocol is a clearly sequenced 7-step workflow with explicit validation checkpoints ('Do not proceed past this point on an unconfirmed recap', 'could I write the recap right now without guessing?') plus feedback loops for error recovery (contradiction handling, scope drift, user override) and a closing Verification checklist. This matches the level-5 anchor of clear sequence with explicit validation and error-recovery loops; not level 4 since checkpoints are explicit rather than minor-gapped. | 5 / 5 |
Progressive Disclosure | The body appropriately splits detail into two existing, one-level-deep references, each clearly signaled with its content summarized ('question-design.md — the 3-4 rule, what makes an option concrete, and when to stop asking'; 'worked-example.md — a fully annotated interview from opening question through recap and confirmation'), with no nested references. Matches the level-5 anchor of a clear overview with well-signaled one-level-deep references; not level 4 since there are no buried or misdirected references. | 5 / 5 |
Total | 17 / 20 Passed |