migrate-oxlint

Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

A highly actionable, well-sequenced migration guide with concrete commands and reference tables, weakened mainly by minor verbosity and a monolithic structure that inlines material which could be split out. It also lacks an explicit run/validate feedback loop.

Suggestions

Tighten or remove inferred-knowledge prose such as the 'high-performance linter...in Rust' intro and the package-manager enumeration (and fix the spurious 'vp install').

Add an explicit validation feedback loop, e.g. after Step 2 run 'npx oxlint' to confirm the migrated config lints cleanly and re-check unmigrated rules before removing ESLint packages.

Move the large plugin-mapping and CLI-option reference tables into a separate reference file (e.g. references/plugin-mapping.md) referenced one level deep from the steps, to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense and actionable, but includes minor unnecessary explanation Claude could infer ("Oxlint is a high-performance linter that implements many popular ESLint rules natively in Rust") and a redundant package-manager aside ("use yarn install, pnpm install, vp install, bun install, etc.") that could be tightened.	2 / 3
Actionability	It provides fully executable commands ("npx @oxlint/migrate", "npm install -D oxlint", "npx oxlint --fix src/"), complete JSON config snippets, and specific plugin/CLI mapping tables that are copy-paste ready, matching the top anchor.	3 / 3
Workflow Clarity	The 5-step sequence is clear and Step 2 offers a review checkpoint ("Review Generated Config", "--details" to check unmigrated rules), but there is no explicit run-and-verify feedback loop; given the config/package replacement is destructive-ish, the guideline caps this at 2 rather than 3.	2 / 3
Progressive Disclosure	Sections are well-organized and the References section links to external docs one level deep, but the ~192-line single file keeps large inline reference material (plugin-mapping and CLI-option tables) that could be split into separate bundle files, fitting the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 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, third-person description that clearly defines both capability and explicit trigger conditions with natural user language. Its only gap is capability breadth (one action rather than several concrete ones).

Dimension	Reasoning	Score
Specificity	It names the domain and core action clearly ("migrating a project from ESLint to Oxlint") but offers a single capability rather than multiple distinct concrete actions, so it sits below the 'lists multiple specific concrete actions' anchor and above the vague/abstract anchor.	2 / 3
Completeness	It explicitly states what it does ("Guide for migrating...") and provides an explicit "Use when..." trigger clause, satisfying both the 'what' and 'when' requirements at the top anchor.	3 / 3
Trigger Term Quality	The phrase "asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint" gives good coverage of natural verbs and entities a user would actually say, matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	The ESLint-to-Oxlint migration niche is narrow with distinct tool-specific 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.