Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is highly actionable with executable code across all four migration steps, but it is verbose for its token budget and underuses the provided reference file. Workflow clarity is decent yet lacks explicit feedback loops for the destructive batch operations involved.
Suggestions
Link references/migration-scripts.md from the body (e.g., a '## Migration Scripts' pointer) and move the overlapping bulk-migration, API-rename, and runbook material out of SKILL.md into that reference to reduce duplication.
Add an explicit validate→fix→retry loop for batch/destructive operations, e.g. when the bulk migration script reports MISMATCH, show the remediation and re-verification steps rather than only printing status.
Trim the Examples section and redundant inline scripts that re-cover Step 1–4 content, keeping SKILL.md as a lean overview that points to the reference for full implementations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly actionable code rather than concept explanation, but it is long and overlaps materially with references/migration-scripts.md (migration functions, API renames, runbook), and the Examples section repeats patterns already covered in the steps, so it could be tightened by deferring to the reference. | 2 / 3 |
Actionability | Provides fully executable Python (plan_cluster_upgrade), SQL (SYNC/CTAS/DEEP CLONE, GRANT, ALTER TABLE TBLPROPERTIES), and bash with concrete old-vs-new API configs and a copy-paste bulk migration script. | 3 / 3 |
Workflow Clarity | Four sequenced steps with a dry-run-first checkpoint and a row-count verification query are present, but for destructive/batch database operations there is no explicit validate→fix→retry feedback loop (the bulk script only prints MISMATCH without a remediation path), which caps this dimension at 2. | 2 / 3 |
Progressive Disclosure | A bundle file references/migration-scripts.md exists, but it is never linked or signaled from the body, and the migration scripts/runbook it contains overlap with inline body content that should have been deferred to it. | 2 / 3 |
Total | 9 / 12 Passed |