Content
70%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 tightly written, well-sequenced investigative workflow rich in domain specifics and validation checkpoints. Its main weakness is that the copy-ready SQL it repeatedly points to lives in a referenced file that is missing from the bundle, which hurts both actionability and progressive disclosure.
Suggestions
Ship references/investigation-queries.md with the skill (or inline the key queries), since the body depends on queries 1, 2, 5, 7, and 8 by number but none are accessible.
Verify the ./references/ path in the body resolves to a real file; a broken reference undermines the one-level-deep navigation the structure otherwise relies on.
Consider inlining at least the boundary query (query 2) and the shape/fingerprint query (query 1) so the core workflow is executable from SKILL.md alone.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and free of basic-concept padding — every section is domain knowledge Claude lacks (warehouse views, fingerprints, merge-queue gate mechanics, Depot cache caveat). A few dense sentences could be trimmed, so it sits just below the fully-lean anchor 5. | 4 / 5 |
Actionability | Names concrete MCP tools and columns, but the 'Copy-ready SQL for every step' is delegated to references/investigation-queries.md (queries 1/2/5/7/8 referenced by number, none inline), and that file is absent — leaving key executable details missing. Not 4 because the gap is not minor; not 2 because substantial concrete guidance remains. | 3 / 5 |
Workflow Clarity | A clearly sequenced investigation flow (triage → fingerprint → shape → boundary → culprit → verify) with explicit validation checkpoints and feedback loops: confidence check before naming anyone, mismatch detection, freshness check via max(created_at), and suspicion of a recent failure-free tail. This is a read-only skill, so the destructive/batch cap does not apply. | 5 / 5 |
Progressive Disclosure | Sections are well-organized and the single external reference is one level deep and clearly signaled, but the referenced file references/investigation-queries.md does not exist in the bundle, so navigation to the bulk of the actionable SQL is broken — a defect beyond the minor organization gaps allowed at anchor 4. | 3 / 5 |
Total | 15 / 20 Passed |