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.
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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 skill description with excellent trigger terms and completeness. It clearly identifies the niche (formatter migration to Oxfmt) and provides explicit 'Use when' guidance with natural keywords. The main weakness is that it could be more specific about the concrete actions involved in the migration process.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Updates configuration files, removes Prettier/Biome dependencies, installs Oxfmt, 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/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: 'migrate', 'convert', 'switch', 'Prettier', 'Biome', 'Oxfmt', 'JavaScript/TypeScript', 'formatter'. These are terms users would naturally use when requesting this task. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — specifically about migrating formatters to Oxfmt. The combination of specific tool names (Prettier, Biome, Oxfmt) and the migration context makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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 strong, well-structured migration guide with excellent actionability—concrete commands, detailed option mapping tables, and clear sequential steps. The workflow is logical and includes important caveats and decision points. The main weakness is that the content is somewhat long for a single file, with detailed reference tables that could be split out, and a few sections that explain things Claude would already understand.
Suggestions
Consider moving the detailed Biome option mapping table and Tailwind option mapping table into separate reference files to keep the main SKILL.md more concise and improve progressive disclosure.
Remove the list of 'Prettier-Compatible Options' that transfer directly—Claude doesn't need to be told which options work the same; only differences and gotchas matter.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and concrete commands, but includes some unnecessary explanations (e.g., listing all Prettier-compatible options that transfer directly, explaining what oxfmt is). The Biome mapping table and some review sections could be tightened, though most content earns its place. | 2 / 3 |
Actionability | Provides fully executable commands (npx oxfmt@latest --migrate prettier/biome), concrete config JSON examples, complete CLI command mappings, and specific option equivalences. Every step has copy-paste ready commands or configurations. | 3 / 3 |
Workflow Clarity | Clear 4-step sequential workflow (migrate → review → configure extensions → update CI/scripts) with explicit notes about failure conditions (e.g., fails if .oxfmtrc.json exists), manual intervention points (overrides, nested config), and decision points (printWidth 80 vs 100). The review step serves as a validation checkpoint. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical progression, and references external docs at the end. However, the detailed Biome option mapping table, unsupported options table, and Tailwind options table could potentially be split into separate reference files to keep the main skill leaner. As a standalone file with no bundle, it's slightly monolithic. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
299d6f8
- Reviewed
Table of Contents
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.