Content
72%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 highly actionable, token-efficient reference with copy-paste-ready commands and complete code examples for the Atlas CLI. Its weaknesses are structural: no explicit validate-then-apply workflow with feedback loops for destructive database operations, and a monolithic single-file layout where detailed material could be split into referenced files.
Suggestions
Add an explicit migration workflow sequence with validation checkpoints (e.g., 1. atlas migrate diff, 2. atlas migrate lint --latest 1, 3. atlas migrate validate, 4. only if clean: atlas migrate apply) with a fix-and-re-lint loop for failures, since these are destructive database operations.
Split detailed material into one-level-deep reference files (e.g., references/linting.md, references/testing.md, references/orm-integration.md) and keep SKILL.md as a lean overview with clearly signaled links.
Replace or qualify pinned version numbers ("docker://postgres/15", "docker://mysql/8") with guidance to use a current engine version, or isolate version-specific examples in a dedicated note, to avoid time-sensitive staleness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Largely lean and code-dominant with almost no padding of concepts Claude already knows, e.g. sections jump straight to executable blocks. Not a 5 because of minor trimmable content: the one-line intro ("Atlas is a language-independent tool for managing database schemas...") and time-sensitive pinned versions ("docker://postgres/15", "docker://mysql/8"). | 4 / 5 |
Actionability | Fully executable throughout: copy-paste-ready CLI commands with flags ("atlas migrate diff add_users --dir \"file://migrations\" --to \"file://schema.sql\"..."), complete HCL schema, atlas.hcl config, lint config, test files, and CI YAML covering the common cases (diff, apply, lint, test, validate, status, baseline, inspect). | 5 / 5 |
Workflow Clarity | Both workflows show a sequence via commands (diff then apply) and validation tools exist ("atlas migrate validate", "atlas migrate lint"), but they appear as separate topical sections rather than an integrated sequence with explicit checkpoints and error-recovery loops. Because this is a database-operations skill, the missing validate-fix-retry feedback loop caps this at 3. | 3 / 5 |
Progressive Disclosure | The ~340-line body has good section headers but everything is inlined in a single file with no references (no references/, scripts/, or assets/ directories exist). Content like the full lint configuration, schema-testing examples, and ORM integration could live in one-level-deep reference files, matching the anchor of inline content that should be separate despite decent organization. | 3 / 5 |
Total | 15 / 20 Passed |