Content
78%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.
This is a tight, instruction-only skill that specifies a concrete interactive method with an explicit feedback loop and stopping conditions, and it correctly keeps everything in one short file. Its main weaknesses are the absence of a worked example, a convoluted transition sentence around AskUserQuestion, and slight redundancy in the direct-question guidance.
Suggestions
Add one compact example of an offer and its reaction (e.g. a candidate and a 'closer but' reply showing how the record is updated) to make the method copy-paste concrete.
Rewrite the transition sentence in plain terms — e.g. 'When the record settles everything reachable sources can settle, ask the user directly (AskUserQuestion) what it still leaves open' — to remove the checkpoint ambiguity.
Merge paragraph 3 with the routing paragraph so the direct-question rule is stated once, trimming the redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — roughly 250 words for a complete elicitation method, assuming Claude's competence with no concept explanations — but there is minor redundancy: paragraph 3 ("If a reaction shows the user would answer a direct question, ask it instead") restates the first clause of the final routing paragraph. This is anchor 4 (efficient with minor instances that could be trimmed), not anchor 5. | 4 / 5 |
Actionability | Guidance is concrete for an instruction-only skill: "offer one concrete thing the user can react to — a candidate, a contrast, a small set laid side by side", reaction types ("a yes, a no, a 'closer but'"), a named tool (AskUserQuestion), and a defined deliverable (hand back the record in confirmed words). It falls short of anchor 5 because there is no worked example of an offer or a short exchange, which would cover the most common case. | 4 / 5 |
Workflow Clarity | The sequence is clear with a genuine feedback loop (offer → read reaction → update record → adjust) and explicit convergence criteria ("until a new offer stops changing the record, or the user says the record matches what they hold"). It is anchor 4 rather than 5 because the transition checkpoint — "Ask what the record leaves open, with AskUserQuestion, once it holds what sources in reach settle" — is convoluted and leaves the handoff moment implicitly defined. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines with no content that belongs in separate files, so a single well-organized SKILL.md is the correct structure per the simple-skill guideline. Cross-references to the **clarify** and **explain** skills are explicit and clearly signaled, and there are no nested or buried references. | 5 / 5 |
Total | 17 / 20 Passed |