migrate-oxfmt

Guide for migrating a project from Prettier or Biome to Oxfmt. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's formatter from Prettier or Biome to Oxfmt.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, token-efficient migration guide with concrete commands and tables. It loses points on workflow clarity (no explicit validate/retry loop) and progressive disclosure (all reference detail inline rather than split into bundle files).

Suggestions

Add an explicit validation checkpoint after Step 1 — e.g., 'Run `npx oxfmt@latest --check` on a sample file; if output differs from Prettier/Biome unexpectedly, review the migrated `.oxfmtrc.json` and re-run migration' — to create a validate→fix→retry loop.

Move the detailed Biome/Prettier option-mapping tables and the unsupported-options list into a bundled reference file (e.g. `references/option-mapping.md`) linked from Step 2, keeping SKILL.md as a lean overview.

Add a brief 'Verify the migration' step that confirms CI passes with `npx oxfmt@latest --check` before considering the migration complete.

Dimension	Reasoning	Score
Conciseness	The body is dense reference material (option-mapping tables, CLI commands, JSON snippets) that assumes Claude knows what formatters are, with no padded conceptual explanation; it uses `oxfmt@latest` to avoid version-pin staleness. Every section earns its place, even though the file is long.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands (`npx oxfmt@latest --migrate prettier`/`biome`), concrete JSON config blocks, and exact CLI replacement mappings for both Prettier and Biome.	3 / 3
Workflow Clarity	Steps 1–4 are clearly sequenced and Step 2 ('Review Generated Config') plus the 'fails if .oxfmtrc.json already exists — delete it first' note act as partial checkpoints, but there is no explicit validate-then-fix feedback loop (e.g., run `oxfmt --check` and correct before proceeding) for a migration that rewrites config and CI, capping this at 2.	2 / 3
Progressive Disclosure	Sections are well organized and the References block links to one-level external docs, but ~200 lines of option-mapping tables all live inline in SKILL.md with no bundled reference files to split the detail into, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with an explicit trigger clause and clear niche. Its only weakness is that the named actions are synonyms for one task rather than a list of distinct capabilities.

Dimension	Reasoning	Score
Specificity	It names the domain and a concrete action (migrating a JS/TS formatter from Prettier/Biome to Oxfmt), but the verbs 'migrate, convert, or switch' are synonyms for a single task rather than multiple distinct concrete actions, so it falls short of the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	It explicitly states what the skill does ('Guide for migrating...') and gives an explicit 'Use when asked to migrate, convert, or switch...' trigger, answering both what and when.	3 / 3
Trigger Term Quality	It covers natural terms a user would say — 'migrate', 'convert', 'switch', 'formatter', 'Prettier', 'Biome', 'JavaScript/TypeScript' — giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific (Prettier/Biome → Oxfmt formatter migration) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: oxc-project/oxc
Commit: eba11de

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.