Content
11%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a hollow template with no actionable content. Despite targeting a complex domain (zero-downtime SQL migrations with rollback plans), it provides no SQL examples, no concrete migration patterns, no validation scripts, and no actual workflow steps. The content reads like a table of contents for a skill that was never written.
Suggestions
Add concrete, executable SQL migration examples for at least one database (e.g., a PostgreSQL expand-contract column rename with specific ALTER TABLE statements and data backfill scripts).
Define an explicit multi-step workflow with validation checkpoints: e.g., 1. Create migration script → 2. Run in staging → 3. Validate row counts/checksums → 4. If errors, execute rollback script → 5. Only when validated, apply to production.
Include a concrete rollback script template paired with a migration script, showing the exact SQL for both forward and backward operations.
Remove generic filler sections ('When to Use', 'Do Not Use', 'Context') and replace the vague 'Instructions' with specific, domain-relevant guidance such as lock-avoidance strategies, batch size recommendations, and concurrent read handling.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with sections that add no value ('When to Use', 'Do Not Use', 'Context') and explains things Claude already knows. The 'Overview' paragraph restates the skill description verbatim. Instructions are generic filler ('Clarify goals, constraints, and required inputs') rather than domain-specific guidance. | 2 / 5 |
Actionability | There is zero concrete, executable guidance anywhere in this skill. No SQL code examples, no specific commands, no migration script templates, no actual rollback procedures. Every instruction is abstract and vague (e.g., 'Apply relevant best practices and validate outcomes'). | 1 / 5 |
Workflow Clarity | Despite the skill being about multi-step migration processes involving destructive/batch operations, there are no sequenced steps, no validation checkpoints, and no feedback loops. The 'Output Format' lists deliverables but provides no workflow for producing them. Database migrations are inherently destructive/batch operations, and the complete absence of validation steps is critical. | 1 / 5 |
Progressive Disclosure | There are no bundle files and no actual references to external files despite mentioning 'implementation playbooks.' The content is a flat, shallow document that neither provides inline detail nor points to supplementary materials. The section structure exists but contains no substantive content worth organizing. | 2 / 5 |
Total | 6 / 20 Passed |