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 lean SKILL.md: no filler, only non-obvious operational rules, and a clean one-level-deep reference structure verified against the actual bundle. The shared weaknesses are mild — a couple of vague tool pointers and operational sequencing/validation living in the reference files rather than in the body.
Suggestions
Replace the vague 'Cost tools' pointer in the budget-setup row of the Quick Reference with the concrete tool names (e.g., 'query_costs', 'create_budget') so every row names explicit tools.
Add one short inline example workflow for the most common intent (e.g., budget health check) with an explicit validate/report checkpoint, so the body demonstrates the expected sequence without relying on references.
In the Workflow section, state explicitly that writes must be confirmed against the reference workflow's checklist before execution, giving the write path a visible validation checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and efficient — every line carries non-obvious, project-specific rules ('Never transform MCP results in a shell or interpreter', 'Report gaps without implying budgets cap spend', 'Never sum or compare across currencies') with zero padding and no explanation of concepts Claude already knows. Nothing to trim. | 5 / 5 |
Actionability | As an instruction-only skill it names concrete tools ('list_budgets', 'forecast_costs', 'query_costs', 'create_budget'), required write parameters ('confirmed scope, amount, thresholds, and recipients'), and a specific error-action table ('Retry once; then stop with the trace ID'). Falls short of 5 because some guidance is vague ('Cost tools' in the setup row) and no inline example covers a common case end-to-end, leaving execution details entirely to references. | 4 / 5 |
Workflow Clarity | The Quick Reference table maps intents to workflows and primary tools, and the 5-step Workflow includes checkpoints ('Distinguish access failures from empty results', 'Retry once; then stop'). Not 5 because the body's steps are general rules rather than a fully sequenced operation — the actual sequences are delegated to references, and there is no explicit validate-before-proceed loop in the body itself. | 4 / 5 |
Progressive Disclosure | A clear overview with a well-signaled Quick Reference linking to four real reference files (budget-health.md, budget-setup.md, guardrails.md, tool-fallback.md — all verified present), each exactly one level deep, with an intent-based navigation table. Matches the anchor-5 structure of concise overview plus well-organized one-level references. | 5 / 5 |
Total | 18 / 20 Passed |