Content
82%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 a dense, highly actionable operational reference with concrete SQL patterns, backend-specific guidance, and clear multi-step workflows backed by error-recovery feedback loops. Its main weaknesses are length/monolith structure (no file splitting for the sizable schema and Cost-Tips material) and some repeatable emphatic phrasing that could be tightened.
Suggestions
Split the Database Schema section and the detailed Cost Tips exploration dimensions into reference files (e.g. SCHEMA.md, COST-TIPS.md) referenced one level deep from SKILL.md to reduce the monolith and improve progressive disclosure.
Tighten the Cost Tips section — consolidate the repeated agent_name filter restatements and trim the duplicated 'do NOT' emphatic warnings now stated in multiple workflows.
Add an explicit validation/checkpoint note to the read-only analysis workflows (Tips, Cost Tips, Improve) — e.g. confirm query results are non-empty before drawing conclusions — to bring workflow clarity to the top anchor.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and assumes Claude's competence (no basic-concept explanations), with non-obvious schema and dialect specifics earning their place; it is not a 5 because the Cost Tips section is expansive and several emphatic 'do NOT' exhortations are repeated and could be trimmed. | 4 / 5 |
Actionability | Fully executable guidance throughout — exact SQL predicates ('WHERE updated_at >= datetime(\'now\', \'-1 day\')'), exact agent_name strings per backend, FTS5 MATCH syntax, quote-escaping rules ('it\'s' → 'it''s'), and concrete output-format templates covering the common cases. | 5 / 5 |
Workflow Clarity | Each workflow is clearly sequenced with numbered steps and includes explicit feedback loops where they matter (query timeout → narrow the window, don't retry; empty results → stop and don't fabricate); read-only analysis workflows lack explicit validation checkpoints, keeping it just below 5. | 4 / 5 |
Progressive Disclosure | Well-organized hierarchical headers (## Workflows, ### per workflow, ## Database Schema, ## Query Guidelines) with in-file cross-references ('re-read the Database Schema section below') providing one-level navigation; not a 5 because it is a ~350-line monolith with no content split into reference files. | 4 / 5 |
Total | 17 / 20 Passed |