Content
60%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, thoughtful workflow skill whose sequencing and verification guidance are strong. Its main weaknesses are repetition that wastes tokens and an abstract diagnostic core: the step that distinguishes the actual cause of a correction, and the step that verifies which skills were invoked, lack concrete procedures or examples.
Suggestions
Add a short worked example (a user correction excerpt → the diagnosis of which skill wording was responsible → the exact resulting edit) to make the abstract diagnostic criteria concrete and imitable.
Name the specific tool or command for 'Verify which skills were actually invoked', the way `read_thread` is named for reading Codex chat references, so that step is executable rather than aspirational.
Cut repeated phrasing — the 'one concrete issue at a time' instruction and the 'let the user's reactions revise the approach' instruction each appear twice in near-identical form — to reclaim tokens without losing guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient, prescriptive instruction, but repeats the same ideas in multiple places — 'examine one concrete issue or suggestion at a time' vs 'Develop one concrete issue at a time', and 'let the user's reactions shape the next attempt' vs 'letting their reactions and the evidence revise the explanation' — and includes rationale sentences ('A better sample response helps judge a skill change') that could be trimmed. | 3 / 5 |
Actionability | There is concrete guidance (use dialectic, use `read_thread` and follow pagination, put proposed intent in a blockquote with bolded words, show exact wording changed, check a materially different request), but the core diagnostic step — 'Determine whether the problem was missing or misleading guidance, competing instructions, skill selection, or failure to apply guidance already present' — names no procedure or tool for 'Verify which skills were actually invoked', and there are no worked examples of a correction-to-edit analysis. | 3 / 5 |
Workflow Clarity | The three sections imply a clear sequence (establish purpose → work backward from the correction → improve the responsible skills) with explicit verification checkpoints ('Show what the changed guidance would produce on the same request', 'check a materially different request for transfer or regression', 'Report what remains unmeasured') and a revisit loop. Not a 5 because the step ordering is implicit in headings rather than explicit, and the entry condition for moving between phases is left to judgment. | 4 / 5 |
Progressive Disclosure | The body is well-organized into headed sections and its references — dialectic, skills-and-instructions, and skills-and-instructions' evaluation guidance — are one level deep, clearly signaled, and each given a stated purpose. Not a 5 because the skill is not structured as an overview over its own detailed materials; all process detail is inlined with only cross-skill links, and some of the diagnosis detail could live in a reference file. | 4 / 5 |
Total | 14 / 20 Passed |