Conciseness

Of 428 lines, roughly 370 explain patterns Claude already knows in detail — Expand-Contract, Strangler Fig, Parallel Run, Canary, Blue-Green, CDC, Lift-and-Shift, circuit breakers, risk categories, generic best-practices lists — plus padded restatement (the Overview and closing paragraph repeat the description verbatim in spirit, and 'Tools and Technologies' restates the Quick Start scripts). Not a 1 because the Quick Start section is genuinely lean and information-dense; clearly below the midpoint because the padding dominates the file.

Actionability

The Quick Start is fully executable (real commands chaining migration_plan.json → compatibility.json → rollback_runbook with concrete asset paths), but it covers only ~20 lines; the remaining bulk is descriptive pattern prose, and the inline code is incomplete — MigrationCircuitBreaker calls self.new_service, self.fallback_to_legacy, self.should_attempt_reset, self.on_success/on_failure without defining them, so it cannot run. Not a 4 because the majority of the body instructs at the direction level ('Track performance and error rates') rather than providing executable steps; above a 2 because the core workflow does give copy-paste commands.

Workflow Clarity

The primary workflow is clearly sequenced with an explicit validation gate: outputs chain between steps, 'exits non-zero unless fully compatible (CI gate)', the migration 'is not approved until' compatibility passes or breaking items are accepted in writing and a rollback runbook exists per phase, with a feedback loop ('Re-run both checks after any schema revision'). Not a 5 because the secondary processes (During-Migration runbook: 'Execute rollback if success criteria not met') leave success criteria and rollback triggers implicit, and the promised expected_outputs shapes for verification are absent.

Progressive Disclosure

The bundle ships three large reference files (migration_patterns_catalog.md, zero_downtime_techniques.md, data_reconciliation_strategies.md — ~99KB combined) but the body never mentions or links any of them, so they are undiscoverable; meanwhile ~300 lines of pattern-catalog content that clearly belongs in those files (and likely duplicates them) are inlined in SKILL.md. The body also cites an 'expected_outputs/' directory that does not exist in the bundle. This matches the anchor for inlined content plus buried references; it reaches a 2 rather than 1 only because section headers and the Quick Start provide some structure.

Specificity

Lists several concrete actions — "Zero-downtime migration planning, compatibility validation, and rollback strategy generation" — plus the migration domains ("system, database, and infrastructure migrations"). Not a 5 because the actions are process-level rather than fully concrete operations (e.g., no mention of generating migration plans/runbooks from specs, the skill's actual executable capability), and no 3 because multiple distinct specific actions are named, not just 1-2.

Completeness

Clearly answers both: the what ("Zero-downtime migration planning, compatibility validation, and rollback strategy generation... Tools for system, database, and infrastructure migrations") and an explicit when clause ("Use when planning a database migration, infrastructure cutover, system replacement, or any high-risk transition that needs explicit rollback paths"). The when lists multiple concrete trigger scenarios, matching the anchor-5 example structure; a 4 would require a vaguer 'when' than what is present.

Trigger Term Quality

Natural triggers include "database migration", "infrastructure cutover", "system replacement", and "rollback paths" — phrases users would realistically say. Not a 5 because common variations are missing: "cloud migration", "data migration", "schema migration/change", "zero-downtime deploy"; not a 3 because coverage goes beyond one or two generic keywords and includes several natural phrasings.

Distinctiveness Conflict Risk

The migration-with-rollback niche ("Zero-downtime migration planning... rollback strategy generation") is clearly distinct from generic processing skills. Not a 5 because "any high-risk transition that needs explicit rollback paths" is broad enough to overlap with deployment/release-management and refactoring skills; not a 3 because the core triggers (database migration, cutover, system replacement) are specific to this niche.