Content
92%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.
A strong, highly actionable skill body: executable examples, explicit validation checkpoints in the migration workflow, and a clean one-level-deep split across four real reference files. The only real cost is token weight — the Common Mistakes table and When to Use section restate content that already appears elsewhere in the skill or frontmatter.
Suggestions
Trim the Common Mistakes table to rows that add new information beyond the body (e.g., the alias-fallback, latest-version-bump, contract-on-staging, and Enterprise rows already covered in Decision Framework and earlier sections), or move it to a reference file.
Compress the "When to Use" section, which duplicates the frontmatter description's triggers; keep only the "Do NOT use for" pointers to sibling skills, which are new information.
Consider condensing the correct/wrong YAML pair in "YAML placement rule" to the rule plus the correct example, since the inverted wrong example largely repeats the same keys.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with genuinely non-obvious dbt Mesh specifics (pointer mechanisms, access resolution, Fusion YAML parsing), but the 17-row Common Mistakes table restates several earlier points (alias fallback, latest-version bump, contract-on-staging, Enterprise gating) and "When to Use" largely duplicates the frontmatter description. Efficient overall with trimmable redundancy — not a 3, since almost nothing explains concepts Claude already knows. | 4 / 5 |
Actionability | Guidance is copy-paste ready throughout: correct/wrong two-argument ref() pairs, a dependencies.yml snippet, correct/wrong YAML config-nesting examples, a runnable verification command (dbt show --inline "select <old_col> from {{ target.schema }}.<unsuffixed_relation>"), and concrete decision trees covering the common cases. | 5 / 5 |
Workflow Clarity | The orientation steps are clearly sequenced (read dependencies.yml → understand ref flow → disambiguate → check patterns → check access), and the migration workflow is a two-deploy sequence with an explicit post-deploy validation step and error-recovery interpretation ("A column does not exist error means latest_version was promoted too early"). Validation is present for these breaking-change operations, so no cap applies. | 5 / 5 |
Progressive Disclosure | SKILL.md serves as a genuine overview (core principle, decision frameworks, common mistakes) while all four referenced files exist, are substantive, clearly signaled via the governance table's Reference column and inline links with anchors, and are one level deep (reference files link only to siblings/own anchors). | 5 / 5 |
Total | 19 / 20 Passed |