Content
86%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.
An exemplary instruction-only router skill: lean shared rules, verified one-level-deep references, and safety gating for deletion-related work. The lower scores reflect that executable detail (worked examples, per-flow step sequences with feedback loops) is fully delegated to reference files rather than surfaced even briefly in the body.
Suggestions
Inline one minimal worked example in the body (e.g., a one-line discovery call with category=Cost, sub-category=IdleResources and its expected savings fields) so the body is self-sufficient for the most common case.
Add a short enumerated step list per major flow (e.g., Discovery: read workflow.md → expand types → read scope-resolution.md → run scoped query) so the top-level sequence is explicit rather than implied by the routing table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, imperative, and assumes competence: "Never substitute billing, inventory or runtime KQL", "Missing amounts are Unavailable, not zero; numeric zero stays zero" — every line is a domain rule Claude could not infer, with no padding or explanations of known concepts. Nothing can be trimmed without losing rule content. | 5 / 5 |
Actionability | Concrete, executable directives are present: exact tool parameters (`category=Cost` and `sub-category=IdleResources`), named legacy fields to avoid ("legacy annualSavingsAmount/savingsAmount"), a required output token ("`Pricing basis: <basis>`"), and a routing table mapping each flow to a specific reference file. It is not a 5 because the body itself contains no worked example — examples are deferred entirely to references/examples.md — so the body alone is not copy-paste ready. | 4 / 5 |
Workflow Clarity | A clear sequence is present (read matching reference per flow → apply shared rules → format response) with explicit checkpoints: "If a required file is unavailable, report it and stop the affected flow", "Visibly show results/proposals before dependent questions", and deletion safety is gated through the Read-only prevalidation reference. It is not a 5 because the per-flow step sequences and validate/retry feedback loops live in the reference files rather than being laid out in the body, leaving the top-level sequence implicit rather than enumerated. | 4 / 5 |
Progressive Disclosure | The body is a lean overview with a quick-reference table routing each flow to a well-signaled, one-level-deep reference; all 10 referenced paths exist in the bundle, the `#read-only-prevalidation` anchor matches a real heading in selection-and-handoff.md, and references link only to siblings or back to SKILL.md (verified: no nested second-level references). Navigation is easy via the table and the README index. | 5 / 5 |
Total | 18 / 20 Passed |