Content
67%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, operationally serious skill body: clear step sequence with dependency ordering and decision gates, a real executable connector command, and correct delegation of templates to a well-organized reference file. Its main weaknesses are redundancy (key boundary rules repeated 3-5 times across sections) and a large fraction of cross-references that point outside the shipped bundle.
Suggestions
State each boundary rule once in the Skill Contract and reference it from the steps instead of repeating it: the ROI/ROAS non-computation rule appears five times and the Retro Card gating conditions three times — consolidating these would materially reduce token cost without losing fidelity.
Trim the dense nested clauses in the Skill Contract 'Reads'/'Promotes' bullets (e.g. the tracker-state and creator_ref provenance rules) into the referenced skill-contract.md, keeping only the operative one-line rule in SKILL.md.
Make bundle-relative references resolvable: within the shipped bundle only references/analysis-templates.md exists, so either inline or bundle the frequently cited shared files (skill-contract.md, measurement-protocol.md, state-model.md) or note that they live in the parent repository.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There is no educational filler, but the same governance rules are restated repeatedly: the ROI/ROAS non-computation boundary appears in Reads, Promotes, step 4, the STAR paragraph, and Next Best Skill, and the Retro Card gating conditions are stated three times (Done-when, step 8, and the 'For the Retro Card' paragraph). This matches 'mostly efficient but could be tightened' rather than score 2, since every sentence is operational rather than padded explanation of known concepts. | 3 / 5 |
Actionability | Concrete guidance is present: eight numbered steps each mapped to a named template step, an executable connector command (python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/youtube.py" videos @creator --limit 20), and a worked example with a filled-in output table. It falls short of fully copy-paste-ready (anchor 5) because much of the executable fill-in detail is deferred to the external templates and several steps are stated as prohibitions rather than executable actions. | 4 / 5 |
Workflow Clarity | The eight steps are clearly sequenced with an explicit dependency rule ("run Step 7 before populating or publishing Step 2 Conversions, Revenue...") and validation gates (measurement-protocol comparability bars, the renew/retest/retire decision gate, Unknown/NEEDS_INPUT fallbacks for missing data). It misses anchor 5 because the dependency flow is convoluted (build the Step 2 shell, then back-fill) and there are no error-recovery feedback loops beyond the fallback labels. | 4 / 5 |
Progressive Disclosure | The body is a genuine overview that correctly delegates the eight fill-in templates to the real one-level-deep references/analysis-templates.md, with a labeled Reference Materials section describing each link. It stops short of anchor 5 because most cross-references (../../../references/skill-contract.md, ../../../references/measurement-protocol.md, scripts/connectors/README.md, and sibling SKILL.md paths) do not resolve within the actual bundle, which contains only references/analysis-templates.md. | 4 / 5 |
Total | 15 / 20 Passed |