CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

Highly actionable and token-efficient migration guidance with strong command and mapping coverage. It falls short on workflow feedback loops for the project-wide change and on splitting detailed reference tables into their own file.

Suggestions

Add an explicit post-migration verification loop (e.g., run `npx oxfmt@latest --check`, review the diff, adjust `.oxfmtrc.json`, re-run) so the batch change has a validate→fix→retry checkpoint.

Move the detailed Biome/Prettier option-mapping tables and unsupported-options lists into a separate reference file (e.g. references/option-mapping.md) and link to it from the relevant steps, keeping SKILL.md as an overview.

Add a brief "Verify the migration" step between Step 2 and Step 3 that confirms generated output matches the prior formatter's behavior before extending the config.

DimensionReasoningScore

Conciseness

Lean reference material (commands, mapping tables, lists) that assumes Claude's competence and never explains what formatters are or how libraries work; every section earns its place.

3 / 3

Actionability

Fully executable, copy-paste-ready guidance: concrete migration commands, complete Biome/Prettier option-mapping tables, and example config JSON blocks.

3 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced with a decision tree and a "Review Generated Config" checkpoint, but this project-wide (batch) change lacks an explicit validate→fix→retry feedback loop after migration, capping it at 2.

2 / 3

Progressive Disclosure

No bundle files exist and external references are clearly signaled, but the single monolithic SKILL.md inlines substantial option-mapping reference tables that would be better split into a separate reference file.

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 concise, well-targeted description with explicit trigger guidance and a clear niche. Its only weakness is that the listed actions are synonyms of a single operation rather than multiple distinct capabilities.

DimensionReasoningScore

Specificity

It names the domain and a concrete action ("migrating a project... formatter"), but "migrate, convert, or switch" are synonyms of one action rather than multiple distinct concrete actions as required for a 3.

2 / 3

Completeness

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..."), in third person.

3 / 3

Trigger Term Quality

Strong coverage of natural terms users would say: "migrate, convert, switch", "formatter", "Prettier", "Biome", "Oxfmt", and "JavaScript/TypeScript".

3 / 3

Distinctiveness Conflict Risk

A clear niche (Prettier/Biome → Oxfmt formatter migration) with distinct triggers that are unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
oxc-project/oxc
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.