Conciseness

No pedagogical padding (Heroku/Terraform familiarity is assumed), but the body duplicates canonical logic it elsewhere forbids: the overlapping 'Workshop resume (mandatory)', 'Gate-presented resume (mandatory)', 'Decision gate resume (mandatory)' and 'Warm start / explicit what-if' paragraphs restate rules owned by INTERPRETER.md and workshop.md, and the ~50-line 'Files in This Skill' tree plus inline dated facts ('no longer accepting new customers as of April 2026', 'not yet live (404)') add trimmable tokens. Not 4 because the duplication spans multiple sections rather than being minor over-explanation; not 2 because everything written is mission-critical operational detail, not explanation of concepts Claude already knows.

Actionability

Concrete executable guidance throughout: a copy-paste tooling probe ('uv --version 2>/dev/null || echo "UV_MISSING"'), exact state fields and values ('run_mode: "decide_and_execute"', 'pricing_source.status'), exact failure outputs ('Unsupported dyno type: {type}. Cannot map to target compute service.'), and a literal offer-line template. Not 5 because the 'Files in This Skill' tree promises a knowledge/design/ sizing-table directory (dyno-eb-sizing.json, postgres-rds-sizing.json, etc.) that does not exist in the bundle, and ../knowledge-base-for-startups/references/offers.md is absent, so some mapped executable resources cannot be loaded as documented.

Workflow Clarity

The 6-phase sequence is explicit with hard ordering ('Clarify must finish before Design, Estimate, or Generate'), explicit gates and feedback loops ('absent or not_run validation is a blocking GATE_FAIL, not a pass'; 'Generate does not complete until the report validator runs successfully'), an error-conditions table with exact stop messages, and a recovery rule ('If unable to complete a step, stop and report the specific issue. Do not fabricate or infer data.'). Not 4 because validation checkpoints are explicit and hard-gated rather than merely present with minor gaps.

Progressive Disclosure

Strong architecture: frontmatter-driven conditional loading with an '~800 lines' per-phase budget, a 'No duplication' canonical-file rule, 'Progressive depth' orchestrator routing, and prose references that all resolve in the actual bundle (spot-checked references/vendored/dsl/INTERPRETER.md, references/phases/estimate/estimate-assemble.md, scripts/validate-heroku-migration-report.py, and 11 others — all present). Not 5 because the 'Files in This Skill' tree is stale against the real bundle: it lists a nonexistent knowledge/design/ directory, omits ~13 existing files (every *-assemble.md fragment, the entire references/vendored/ subtree, shared/report-decision-core.md), so map-only navigation would fail; not 3 because operative references are clearly signaled and accurate.

Specificity

Multiple concrete third-person actions with comprehensive domain coverage: 'discover Heroku resources live via the authenticated Heroku CLI (read-only, consent-gated) and/or from Terraform, Procfile/app.json, and billing exports', then 'clarify, design, estimate costs, generate artifacts, and collect feedback', with named service mappings (Heroku Postgres to RDS, Heroku Redis to ElastiCache, Heroku Kafka to MSK, dynos to Elastic Beanstalk/Fargate). Not 4: discovery sources, all six phases, and the workshop repricing are all enumerated — no coverage gaps remain.

Completeness

Explicitly answers both questions: what — 'Runs a 6-phase process: discover… Then clarify, design, estimate costs, generate artifacts, and collect feedback' — and when — 'Triggers on: migrate from Heroku, Heroku to AWS, move off Heroku…', plus explicit exclusions ('Do not use for: GCP migrations (see gcp-to-aws), Azure migrations (see azure-to-aws), AWS-to-Heroku reverse migration…'). Not 4: the 'when' is a concrete trigger list, not merely present-but-could-be-more-explicit.

Trigger Term Quality

Thirteen explicit natural trigger phrases — 'migrate from Heroku', 'move off Heroku', 'leave Heroku', 'Heroku to ECS', 'what-if workshop', 'compare migration scenarios', plus service-specific variants ('migrate Heroku Postgres to RDS', 'migrate dynos to Fargate'). Not 4: synonyms and phrasing variants a user would actually say are comprehensively covered for this domain.

Distinctiveness Conflict Risk

Clear niche (Heroku-to-AWS migration) with distinct service-level triggers and explicit disambiguation against sibling skills: 'Do not use for: GCP migrations (see gcp-to-aws), Azure migrations (see azure-to-aws), AWS-to-Heroku reverse migration, general AWS architecture advice without migration intent, or Heroku-to-Heroku refactoring'. Not 4: the negative scope plus specific triggers leave minimal overlap risk with any neighboring skill.