Conciseness

The body teaches no background concepts and consists almost entirely of Oxfmt-specific facts Claude cannot know (option mappings, defaults, failure conditions, plugin handling). The only redundancy is nested-config guidance appearing in both Step 1 and Step 2, which is minor and cross-referenced, so it stays at anchor 5 rather than dropping to anchor 4's 'minor instances of over-explanation'.

Actionability

Commands are copy-paste ready ("npx oxfmt@latest --migrate prettier"), the Biome-to-Oxfmt option mapping is an exact per-option table, JSON snippets are complete, and the Before/After CI table covers the common cases for both sources. This matches anchor 5's 'fully executable; copy-paste ready; covers the common cases'.

Workflow Clarity

A clear five-step sequence (migrate, review config, configure extensions, update CI, review diff) with documented failure conditions ("Fails if no Prettier config is found", "Fails if an Oxfmt config ... already exists") and a Step 5 review checkpoint that classifies divergences as intentional vs. bug. It is below anchor 5 because the feedback loop after the batch reformat is implicit — there is no explicit 'if the diff looks wrong, revert or report and retry' instruction — but validation checkpoints are present, so the batch-operation cap at 3 does not apply.

Progressive Disclosure

A single well-organized SKILL.md with numbered step sections, consistent tables, clearly labeled notes, and an external References list. The inlined option mappings are working instructions needed during the migration itself, not misplaced reference material, giving good structure per anchor 4. It is not anchor 5 because the skill is well over 50 lines with no internal reference split (e.g., the plugin/option tables could live in reference files), and not anchor 3 because navigation and signaling are clear.

Specificity

"Guide for migrating a project from Prettier or Biome to Oxfmt" names the domain and both concrete source tools, but describes a single action rather than enumerating several capabilities (e.g., config migration, ignore-file migration, CI updates). It is above anchor 2 because the named tools make it concrete, but below anchor 4 because only one action is listed.

Completeness

It explicitly answers both 'what' ("Guide for migrating a project from Prettier or Biome to Oxfmt") and 'when' ("Use when asked to migrate, convert, or switch a project's formatter..."), with concrete trigger phrases. This matches the anchor-5 example structure, not anchor 4 where the 'when' is only weakly specified.

Trigger Term Quality

"Use when asked to migrate, convert, or switch a project's formatter from Prettier or Biome to Oxfmt" covers three natural verb synonyms and all three tool names. It falls short of anchor 5, which expects synonyms plus file extensions or config-file names (e.g., .prettierrc, biome.json), but exceeds anchor 3's 'missing common variations'.

Distinctiveness Conflict Risk

"from Prettier or Biome to Oxfmt" carves out a clear niche with named tools and distinct triggers; there is minimal risk this description fires for an unrelated skill.