Content
88%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 router skill: clear mode selection with explicit required-input contracts, strong validation gates (especially for the batch index-push channel), and clean one-level-deep progressive disclosure into four substantive play packs. The main costs are duplicated routing/scope prose across sections and a command reference to a script that is not part of the visible bundle.
Suggestions
Collapse the duplicated next-skill routing: keep the mode-conditional branches in one place (either 'Skill Contract → Primary next skill' or 'Next Best Skill') and reference it from the other, cutting ~10 lines.
Merge the three scope statements (intro paragraph, instruction 5, 'Scope guard') into one, e.g. keep the intro paragraph and reduce the 'Scope guard' section to a one-line pointer.
Verify 'scripts/connectors/indexpush.py' ships with the skill (or move the index-push command into the programmatic/local reference packs with a note on where the script lives), so the referenced path resolves from the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and largely lean — no explanations of concepts Claude already knows, and tables carry the mode/data-source information efficiently. However, content is systematically duplicated: the next-skill routing appears both in 'Skill Contract → Primary next skill' and again in full in 'Next Best Skill', and the scope statement appears in the intro, instruction 5, and again as the 'Scope guard' paragraph. Anchor 4 ('efficient; minor instances that could be trimmed') fits; not 3 because there is no padded or unnecessary conceptual explanation, only structural repetition. | 4 / 5 |
Actionability | For an instruction-only router skill the guidance is fully concrete: a mode-selector table with required inputs and an explicit NEEDS_INPUT contract, named guardrail mechanisms (N-gram dedup, site-reputation-abuse, '[needs source]' flags), exact filename templates per mode, and a copy-paste command with flags and a dry-run default ('python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/indexpush.py" indexnow --file new-urls.txt --key $INDEXNOW_KEY'). Per the rubric's code-vs-instruction note, the absence of code beyond the one command is not penalized. | 5 / 5 |
Workflow Clarity | A numbered 5-step sequence with explicit validation checkpoints: stop-and-ask on ambiguous mode ('do not guess'), NEEDS_INPUT return when the required input is missing or inconsistent, guardrail application before handoff with 'flag any blocker; do not ship it silently', and the batch index push is explicitly gated ('push only after the thin/duplicate guardrail passes', dry-run by default). Each reference pack carries its own numbered play and 'Done when' line, satisfying the batch-operation feedback-loop requirement. | 5 / 5 |
Progressive Disclosure | SKILL.md is a clean overview pointing to four real one-level-deep play packs, each summarized with its contents in 'Reference Materials', and the reference files cross-link each other without nesting further. Not 5 because the body invokes 'scripts/connectors/indexpush.py' (and links suite-level files like skill-contract.md, CONNECTORS.md, humanizer-slop.md) that are not present in the provided bundle — a minor navigation gap against the actual file listing. | 4 / 5 |
Total | 18 / 20 Passed |