Conciseness

The body is lean and assumes Claude's competence — no tutorials on CSP, JSON, or grep — with every step carrying domain-specific value. It is not 5 because Step 2 contains a mildly redundant pair of JSON examples (the 'After (correct)' deployments snippet followed immediately by another full app.json snippet showing the infra placement) that could be merged and trimmed.

Actionability

Fully executable throughout: copy-paste-ready grep commands ('grep -rn "fetch\|axios\|new XMLHttpRequest" src/ --include="*.ts" --include="*.tsx"'), exact JSON shapes for app.json and manifest.json, exact deploy script lines ('npx @cognite/cli@latest apps deploy --interactive'), and explicit delegation to setup-flows-auth. Covers the common cases including the empty-network edge case ('If no external calls exist, leave "network": []').

Workflow Clarity

Six clearly sequenced steps with an audit-before-change checkpoint (Step 1 report template), skip-if-already-done conditions ('If `infra` is already "appsApi", skip this step'), a verification pass (Step 6 grep for leftover Dune references), a completion checklist, and user-facing next steps. This matches the 5 anchor: explicit validation, feedback, and checklists are all present.

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and none are needed — the entire skill fits appropriately inline as a single well-organized SKILL.md with clear section headers. The one cross-file dependency (the setup-flows-auth skill) is clearly signaled in its own step. Per the simple-skill guidance, well-organized sections with no need for external references score 5.

Specificity

The description lists five concrete, verifiable actions ('audits current state, updates app.json to appsApi infra, delegates auth wiring to setup-flows-auth, creates or updates manifest.json network permissions, and updates deploy scripts to @cognite/cli'), giving comprehensive coverage of the migration. Not 4 because there are no coverage gaps — every phase of the migration is named.

Completeness

Both questions are answered explicitly: what ('Orchestrates the full migration: audits... updates... delegates... creates... updates...') and when ('Use this whenever a user says...') with concrete trigger phrases. Matches the 5 anchor exactly; not 4 because the 'when' clause is fully explicit, not merely present.

Trigger Term Quality

It quotes natural user phrasings directly: 'migrate to Flows', 'migrate to new infra', 'move from dune to flows', 'migrate legacy app', plus 'wants to move their existing app to the new Flows app hosting'. These cover the synonyms and informal variations a user would actually say; not 4 because no common natural phrasing is missing.

Distinctiveness Conflict Risk

The description occupies a clear niche (legacy Dune app to Flows appsApi hosting) with named tools and files (app.json, manifest.json, @cognite/cli, setup-flows-auth), so it is unlikely to trigger for the wrong skill. Not 4 because there is no meaningful overlap with adjacent skills — the domain is highly specific.