Content
75%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 high-quality, safety-focused skill body: actionable code and commands, clear sequenced workflow with validation, and well-structured sections with clearly signaled doc references. Main gaps are a missing explicit error-recovery feedback loop in the main workflow and a few trimmable prose passages.
Suggestions
Add an explicit feedback loop to the Workflow section's Validate step: 'If sqlmigrate/tests fail, fix the migration and re-run before proceeding' — the destructive/batch nature makes the validate->fix->retry cycle especially important.
Trim rhetorical padding (e.g. 'Be honest:', 'Genuinely intentional, reviewed deletions') and tighten long hazard explanations to their rule-motivating core to recover tokens.
For patterns currently deferred to safe-django-migrations.md, consider inlining a one-line executable summary of each (e.g. the SeparateDatabaseAndState skeleton) so the skill is actionable without opening the external doc.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense and assumes competence — it explains genuinely non-obvious Postgres/PostHog internals (lock ordering, deferred constraints, db_default vs default) rather than basics Claude already knows — with only minor sentences of rhetorical padding ('Be honest:', 'Genuinely intentional, reviewed deletions') that could be trimmed. | 4 / 5 |
Actionability | Gives concrete, copy-paste-ready code (callable choices, db_default example, RunSQL) and exact commands (DEBUG=1 ./manage.py makemigrations, sqlmigrate, rg grep) plus named helpers (SafeDropTable, deprecate_field, untrack_field), but defers several patterns to safe-django-migrations.md rather than inlining them. | 4 / 5 |
Workflow Clarity | The Workflow section sequences Classify -> Generate -> Apply safety rules -> Validate with a validation checkpoint, and the retire-table/retire-column sub-workflows include deploy-cycle waits; it avoids the destructive-skill cap because validation is present, but lacks an explicit 'if validation fails, fix and retry' feedback loop in the main workflow. | 4 / 5 |
Progressive Disclosure | Well-organized with clear section headers and one-level-deep references signaled via 'Read these files first' and 'Full guide:' pointers (safe-django-migrations.md, schema-changes.md); no bundle files exist, and some hazard detail that could live in references is inlined, but that is appropriate for load-bearing safety rules. | 4 / 5 |
Total | 16 / 20 Passed |