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

83%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

This is a well-structured, highly actionable migration guide with clear sequential steps and concrete commands throughout. Its main weakness is length — several detailed reference tables (Biome mappings, unsupported options, compatible options) could be extracted to separate files to improve token efficiency. The workflow is well-sequenced with appropriate validation checkpoints and error handling notes.

Suggestions

Extract the Biome option mapping table, unsupported Prettier options table, and 'Prettier-Compatible Options' list into a separate REFERENCE.md file to reduce the main skill's token footprint.

Remove the 'Prettier-Compatible Options' section entirely — listing options that 'transfer directly with the same behavior' adds no actionable value for Claude.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good use of tables and concrete commands, but includes some unnecessary content like the full list of 'Prettier-Compatible Options' that transfer directly (Claude doesn't need to be told these work the same), and some explanatory text that could be trimmed. The Biome mapping table and unsupported options tables earn their place, but overall it could be tighter.	2 / 3
Actionability	Fully executable commands throughout (npx oxfmt@latest --migrate prettier, CLI replacements), concrete JSON config examples, specific option mapping tables, and copy-paste ready before/after command comparisons. Every step has concrete, actionable guidance.	3 / 3
Workflow Clarity	Clear 4-step sequential workflow (run migration → review config → configure extensions → update CI/scripts) with explicit notes about failure conditions (e.g., fails if .oxfmtrc.json already exists), manual intervention points (overrides, printWidth decision), and specific review checkpoints after the automated migration step.	3 / 3
Progressive Disclosure	The skill has good section structure and ends with external references, but it's quite long (~200 lines) with detailed mapping tables and option lists that could be split into separate reference files. The Biome option mapping table, unsupported options table, and Prettier-compatible options list could live in referenced files to keep the main skill leaner.	2 / 3
	Total	10 / 12 Passed

Description

89%

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

This is a solid description with clear 'what' and 'when' clauses, strong trigger terms covering natural user phrasing, and a highly distinctive niche. The main weakness is that it could be more specific about the concrete actions involved in the migration process (e.g., updating config files, removing dependencies, adjusting rules).

Suggestions

Add specific concrete actions to improve specificity, e.g., 'Removes Prettier/Biome config, installs Oxfmt, updates package.json scripts, and adjusts formatting rules.'

Dimension	Reasoning	Score
Specificity	It names the domain (formatter migration) and the specific tools involved (Prettier, Biome, Oxfmt), but doesn't list concrete actions like 'update config files, remove old dependencies, adjust formatting rules'.	2 / 3
Completeness	Clearly answers both 'what' (guide for migrating from Prettier or Biome to Oxfmt) and 'when' (explicit 'Use when asked to migrate, convert, or switch...' clause with specific trigger scenarios).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'migrate', 'convert', 'switch', 'Prettier', 'Biome', 'Oxfmt', 'JavaScript/TypeScript', 'formatter'. These cover the common ways a user would phrase such a request.	3 / 3
Distinctiveness Conflict Risk	Very specific niche — migrating specifically from Prettier/Biome to Oxfmt. This is unlikely to conflict with other skills due to the narrow, well-defined scope involving specific tool names.	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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: oxc-project/oxc
Commit: 30116a3

Reviewed: 2 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.