Content
66%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 orchestrator skill with excellent sequencing, gates, and resume/acceptance mechanics, but its token budget suffers from meaningful duplication — the heartbeat doctrine and several constant rules each appear twice or more. Unbound shell variables in otherwise copy-paste-ready snippets slightly reduce executability.
Suggestions
Deduplicate the heartbeat/external-cadence material: keep a one-line pointer at the top and retain the full doctrine (resolver chain, pivot rules) in only one place — either the single section or the referenced shared-references/external-cadence.md.
Bind $ROOT, $RUN_ID, and $STAGE where they are first used in the run-state and heartbeat sections so the bash snippets are directly executable.
Collapse the repeated AUTO_PROCEED/VENUE/RENDER_HTML explanations (Constants, Checkpoint execution rule, Gate sections, Key Rules) into one canonical statement, leaving the other mentions as one-line cross-references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The heartbeat/external-cadence doctrine appears nearly wholesale twice (the "⏱ External cadence" blockquote and the "Overnight heartbeat" section, each with its own copy of the helper-resolution chain), and AUTO_PROCEED, VENUE, and RENDER_HTML rules are each restated across Constants, the "Checkpoint execution rule", the gate sections, and "Key Rules". That is several padded/redundant sections rather than a single tightening opportunity, so it sits below the mostly-efficient anchor of 3, though it never drifts into explaining concepts Claude already knows (not 1). | 2 / 5 |
Actionability | Guidance is largely executable: exact sub-skill invocations ('/experiment-bridge "$CHOSEN_IDEA_TITLE" — code review: $CODE_REVIEW, base repo: $BASE_REPO'), concrete state commands ('run_state.py start <root> <run_id> --phases "..."'), and a copy-paste bash resolver chain. It falls short of fully executable because $ROOT, $RUN_ID, and $STAGE are used in the heartbeat/run-state snippets without ever being bound, and several code blocks are templates with unresolved placeholders. | 4 / 5 |
Workflow Clarity | The five stages are clearly sequenced with explicit validation: an acceptance table per phase ("Mark `accepted` ONLY after the stage's gate passes"), cross-model gates, re-validation of done-but-unaccepted stages on resume, and feedback loops (sanity check with "auto-debugs failures (up to 3 attempts)", stop at round 4 without positive assessment, non-blocking render failure handling). This matches the top anchor's explicit checkpoints plus error-recovery loops. | 5 / 5 |
Progressive Disclosure | Detail is appropriately delegated via clearly signaled one-level links (shared-references/reviewer-backends.md, external-cadence.md, resumable-runs.md, the Output Protocols section, templates/RESEARCH_BRIEF_TEMPLATE.md). It is not 5 because the heartbeat doctrine is duplicated inline instead of fully delegated to the referenced file, and the referenced bundle files live outside this skill's directory (no references/ or scripts/ exist here), so navigation depends on unverifiable sibling paths. | 4 / 5 |
Total | 15 / 20 Passed |