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

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/migrate-oxlint/SKILL.md

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 description with excellent trigger terms and completeness, clearly specifying both what the skill does and when to use it. The main weakness is that the 'what' portion is somewhat high-level ('Guide for migrating') rather than listing specific concrete migration actions. Overall it would perform well in skill selection among a large set of skills.

Suggestions

Add specific concrete actions to improve specificity, e.g., 'Handles config file conversion, rule mapping, dependency updates, and CI pipeline adjustments for migrating from ESLint to Oxlint.'

Dimension	Reasoning	Score
Specificity	Names the domain (linter migration from ESLint to Oxlint) and the general action (migrating/converting), but doesn't list specific concrete actions like 'update config files, remove ESLint dependencies, map ESLint rules to Oxlint equivalents, update CI pipelines'.	2 / 3
Completeness	Clearly answers both 'what' (guide for migrating from ESLint to Oxlint) 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', 'ESLint', 'Oxlint', 'JavaScript/TypeScript', 'linter'. These are terms users would naturally use when requesting this task.	3 / 3
Distinctiveness Conflict Risk	Very specific niche — ESLint-to-Oxlint migration is a narrow, well-defined task unlikely to conflict with other skills. The combination of both tool names creates a distinct trigger profile.	3 / 3
	Total	11 / 12 Passed

Implementation

64%

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

This is a solid, actionable migration guide with clear step-by-step instructions and concrete commands. Its main weaknesses are the lack of explicit validation/verification checkpoints in the workflow (e.g., running oxlint after config generation to confirm it works) and the amount of reference material inlined that makes the document longer than necessary. The Tips section in particular contains many items that could be trimmed or moved to a separate reference file.

Suggestions

Add explicit validation steps after key stages — e.g., 'Run `npx oxlint` after Step 2 to verify the generated config works without errors' and 'Run your CI pipeline or test suite after Step 5 to confirm the migration is complete'.

Move the plugin mapping table and CLI options comparison table to a separate REFERENCE.md file, keeping only the most essential information inline to reduce token usage.

Trim the Tips section significantly — many items (output formats list, editor configuration, .gitignore behavior) are either discoverable from docs or unnecessary for Claude to have in context.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary content. The overview paragraph explaining what Oxlint is and the plugin mapping table are reference material Claude could look up. The Tips section is lengthy and could be trimmed. Some explanatory phrases like 'use yarn install, pnpm install, vp install, bun install, etc. depending on your package manager' are unnecessary for Claude.	2 / 3
Actionability	The skill provides concrete, executable commands at every step (npx @oxlint/migrate, npm install -D oxlint, npx oxlint src/), specific CLI option tables, real JSON config examples, and clear before/after command mappings. Everything is copy-paste ready.	3 / 3
Workflow Clarity	The 5-step sequence is clearly laid out and logically ordered. However, there are no explicit validation checkpoints or feedback loops — for instance, after generating .oxlintrc.json there's no 'run oxlint and verify it passes' step, and after updating CI scripts there's no verification step. For a migration workflow that could break CI, validation steps are important.	2 / 3
Progressive Disclosure	The content is well-structured with clear headings and sections, and external references are provided at the end. However, the plugin mapping table, rule categories explanation, CLI options tables, and the lengthy Tips section make this quite long and could benefit from being split into separate reference files. With no bundle files, all content is inline in a single document.	2 / 3
	Total	9 / 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: 299d6f8

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