Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is a well-structured orchestration skill: highly actionable with concrete sub-skill invocations and templates, clearly sequenced phases with checkpoints and feedback loops, and clean one-level-deep references. The main weakness is verbosity from restating the pipeline and embedding full dialog/report templates that could be condensed.
Suggestions
Remove redundant restatements of the pipeline diagram — it appears in the overview, the Phase 5 report template, and the Composing section; keep one canonical version and reference it.
Condense the checkpoint dialog templates to the essential prompts rather than full scripted blocks, or move the complete report markdown template into a reference file to slim the SKILL.md body.
Tighten the repeated 'What this does' bullet lists where they duplicate information already conveyed by the invocation command and constants.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is task-focused and avoids explaining concepts Claude already knows, but the pipeline is restated three times (overview diagram, Phase 5 report template, Composing section) and the checkpoint dialog templates plus the full report template add bulk that could be tightened, fitting the 'mostly efficient but could be tighter' anchor rather than the lean level 3. | 2 / 3 |
Actionability | Provides copy-paste-ready invocations (e.g. `/research-lit "$ARGUMENTS"`, `/novelty-check "[top idea 1 description]"`), concrete constants (PILOT_MAX_HOURS, MAX_TOTAL_GPU_HOURS), exact checkpoint wording, and a full markdown report template — fully executable and specific. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced into Phases 1–5 with explicit 🚦 checkpoints between phases, feedback loops for error recovery ("repeat until the user is satisfied", "repeat until the user selects at least 1 idea"), and validation gates (pilot signal, novelty elimination), matching the anchor for clear sequence with explicit validation and feedback loops. | 3 / 3 |
Progressive Disclosure | No bundle files are present, but the body is well organized into overview/constants/phases/output sections and keeps references one level deep (the shared Output Protocols links are clearly signaled under a dedicated section), so navigation is easy and no monolithic or deeply nested references appear. | 3 / 3 |
Total | 11 / 12 Passed |