Content
62%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.
The process itself is excellent: a well-gated three-phase workflow with specific counts, tool usage, a concrete output template, and a verification checklist. The two real defects are triplicated anti-pattern/red-flag content wasting tokens, and three referenced bundle files (frameworks.md, refinement-criteria.md, examples.md) that do not exist, leaving the skill's detail layer broken.
Suggestions
Create the referenced bundle files (frameworks.md, refinement-criteria.md, examples.md) — or remove the references and inline the essential Phase 2 evaluation criteria — since all three are currently dead ends for anyone following the instructions.
Merge 'Anti-patterns to Avoid', 'Common Rationalizations', and 'Red Flags' into a single section; they repeat the same five points nearly verbatim three times, wasting roughly 40 lines of token budget.
Since the 'full evaluation rubric' in refinement-criteria.md is missing, inline the complete stress-test criteria for user value, feasibility, and differentiation so Phase 2 can be executed without the broken reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core process, phases, and output template are tight and earn their tokens, but three sections repeat the same points nearly verbatim: "5-8 well-considered variations beat 20 shallow ones. Quality over quantity" appears in both Anti-patterns and the Common Rationalizations table, as do "A yes-machine produces weak ideas", "Untested assumptions are the #1 killer", and "The Not Doing list is arguably the most valuable part", with Red Flags restating them a third time. Mostly efficient, but a clear tightening opportunity — fits the 3 anchor; not 2 because the process guidance itself is not padded. | 3 / 5 |
Actionability | Strong concrete guidance exists — specific counts ("Ask 3-5 sharpening questions", "Generate 5-8 idea variations"), named tools (AskUserQuestion, Glob/Grep/Read), a full copy-paste output template, and a save path. But it instructs "Read `frameworks.md`", "Read `refinement-criteria.md` for the full evaluation rubric", and "Read `examples.md`" — none of these files exist in the bundle, so key details (especially the full Phase 2 rubric) are missing. Concrete but incomplete matches the 3 anchor better than 4. | 3 / 5 |
Workflow Clarity | Three phases are clearly sequenced with explicit checkpoints and gating: "Do NOT proceed until you understand who this is for and what success looks like", Phase 2 only "After the user reacts to Phase 1", "Only save if they confirm", and a final Verification checklist. This matches the 5 anchor (clear sequence, explicit validation steps, checklist for a complex process); this is a conversational, non-destructive skill so the destructive-operation cap does not apply. | 5 / 5 |
Progressive Disclosure | The body is well-structured with sections, and detail is deferred via clearly signaled one-level-deep references ("Read `frameworks.md` in this skill directory", "Read `refinement-criteria.md`", "Read `examples.md`"). However, none of those three files exist in the bundle — only scripts/idea-refine.sh is present — so the navigation is broken and the deferred content is unavailable. Not 4/5 because the references point to nonexistent files; not 2 because the in-body structure and signaling themselves are good. | 3 / 5 |
Total | 14 / 20 Passed |