The description lists no concrete actions or capabilities. It only specifies trigger phrases and vaguely mentions 'migrate infrastructure between providers, graduate from PaaS to IaC, consolidate providers, or partially move specific services' without describing what the skill actually does (e.g., generates Terraform configs, creates migration plans, etc.).

The 'when' is thoroughly covered with extensive trigger phrases, but the 'what' is extremely weak — there is no clear explanation of what the skill actually does beyond vague references to migration. The description is essentially all triggers with no capability description.

Excellent coverage of natural trigger terms including specific phrases like 'move to AWS', 'move from heroku', 'switch providers', 'graduate from PaaS', 'cloud migration', and many variations users would naturally say. Covers multiple cloud providers and common PaaS platforms.

The description carves out a very clear niche around infrastructure migration between cloud providers and PaaS graduation. The specific trigger terms like 'move from heroku', 'move to AWS', 'consolidate providers' are highly distinctive and unlikely to conflict with other skills.

The skill is extremely verbose at ~400+ lines. It explains many concepts Claude already understands (what PaaS graduation means, what DNS TTL is, what data integrity checks are). Many sections could be condensed significantly—e.g., the migration scenarios, cost comparison table template, and error handling section all contain explanatory padding that doesn't add actionable value.

The skill provides concrete CLI commands (gh issue create, gh issue edit) and structured agent invocation patterns, but much of the core migration work (IaC generation, data migration, DNS cutover, traffic shifting) is described abstractly rather than with executable specifics. Steps like 'Apply the generated IaC to staging' and 'Set up parallel running' are vague directives without concrete commands.

The workflow is clearly sequenced across 10 steps with explicit dependencies, validation checkpoints (staging verification before cutover, pre-cutover checklist), feedback loops (rollback procedure at Step 9 with retry/skip/abandon options), and clear state transitions (label changes tracking migration status). The rollback handling is thorough with per-step recovery.

The skill references external files (migration-scenarios.md, migration-checklist.md, experience-derivation.md, providers.md, environments.md) but no bundle files are provided to verify their existence or content. The SKILL.md itself is monolithic—the migration plan template, cost comparison format, issue templates, and error handling could be split into reference files. The references that do exist are reasonably signaled but the main file carries too much inline content.