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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

The body is an actionable, well-structured migration guide with executable commands and thorough option mappings. Its main gap is the absence of an explicit validation/verification checkpoint after migration to confirm formatting behavior.

Suggestions

Add a final verification step to the workflow, e.g. 'Run npx oxfmt@latest --check to confirm the migrated config formats the project as expected; if output differs undesirably, revisit Step 2 options.'

Tighten the 'Notes (both sources)' and per-source notes by merging overlapping bullets (e.g. the .oxfmtrc.json-exists failure and blank-config fallback could be one concise list).

DimensionReasoningScore

Conciseness

Dense, reference-oriented content with no padding about what formatters are; option-mapping tables are token-efficient. A few explanatory notes could be trimmed slightly, but every section earns its place.

4 / 5

Actionability

Copy-paste-ready commands (e.g. 'npx oxfmt@latest --migrate prettier'), complete JSON config examples, and full source-to-target option mapping tables cover the common Prettier and Biome cases.

5 / 5

Workflow Clarity

Clear four-step sequence with a useful static/dynamic/nested decision tree in Step 1 and a review checkpoint in Step 2, but it lacks an explicit post-migration validation step (e.g. run 'oxfmt --check' to confirm output).

4 / 5

Progressive Disclosure

Well-organized into Overview, Steps 1–4, Tips, and a clearly signaled one-level-deep References section linking external docs; no bundle files exist, and inline mapping tables are appropriately placed as core migration material.

4 / 5

Total

17

/

20

Passed

Description

82%Weight 40%Scale 1-5

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

The description is well-crafted: third-person voice, explicit 'Use when' trigger clause, and a clearly bounded niche. Its only weakness is that the listed actions are synonyms for one operation rather than a broad action set.

DimensionReasoningScore

Specificity

Names the domain (migrating a JS/TS formatter from Prettier/Biome to Oxfmt) and the core action, but 'migrate, convert, or switch' are synonymous variants of a single action rather than multiple distinct concrete actions.

3 / 5

Completeness

Explicitly answers both what ('Guide for migrating...') and when ('Use when asked to migrate, convert, or switch...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keyword coverage ('migrate', 'convert', 'switch', 'Prettier', 'Biome', 'formatter') that users would actually say; only minor synonyms like 'reformat' are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Prettier/Biome → Oxfmt formatter migration) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

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.