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.
The body is well-structured and highly actionable, with a dense routing table, clear workflow, and concrete output templates. The main weakness is conciseness: editorial "killer command" framing is repeated and could be trimmed without losing clarity.
Suggestions
Collapse the intro's "killer command" pitch and the standalone "Why This Is the Killer Command" section into one or two sentences; the rationale is restated and adds padding.
Add the literal invocation syntax for routing to a cs-* agent (e.g., the exact command or tool call) so the single-role workflow step is copy-paste ready rather than "invoke that cs-* agent directly."
Consider moving the full 14-row signal→route table into a references file with a compact summary inline, so the SKILL.md body stays an overview and progressive disclosure reaches the top anchor.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The routing table and examples are dense and efficient, but "killer command" framing is repeated across the intro and a dedicated "Why This Is the Killer Command" section that restates the cognitive-tax rationale, which could be tightened; matches "mostly efficient but includes some unnecessary explanation." | 3 / 5 |
Actionability | A signal→agent routing table, numbered workflow, and copy-paste output templates make the guidance mostly executable; not a 5 because the actual agent-invocation step is described as "invoke that cs-* agent directly" without a literal command syntax. | 4 / 5 |
Workflow Clarity | A clear five-step sequence handles single-role, multi-role, and ambiguous cases, with the ambiguous branch feeding back through /cs:office-hours and a decision-log step; minor validation gap keeps it below 5. Routing is not destructive or batch, so the workflow cap does not apply. | 4 / 5 |
Progressive Disclosure | A single self-contained file is well sectioned (Routing Logic, Workflow, Output, Examples, Related) and the Related links are one level deep and clearly signaled; not a 5 because the sizable routing table has no progressive detail reference for this skill's own content. | 4 / 5 |
Total | 15 / 20 Passed |