CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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 content is a high-quality, actionable migration guide with executable commands, clear sequencing, and well-organized sections. Minor gains are available from trimming light over-explanation, adding an explicit validation feedback loop, and moving dense reference tables into a bundled reference file.

Suggestions

Trim contextual asides Claude already knows (e.g., the 'high-performance linter...natively in Rust' framing and the 'likely unnecessary unless non-standard name' aside) to tighten conciseness.

Add an explicit validation feedback loop after Step 2 (e.g., run oxlint on the project, review new errors, adjust .oxlintrc.json, re-run) to lift workflow_clarity.

Move the plugin-mapping table and full CLI/option reference into a bundled references/ file (e.g. PLUGIN-MAPPING.md) and link to it from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-paste commands and dense tables, but contains minor over-explanation that could be trimmed (e.g., "Oxlint is a high-performance linter that implements many popular ESLint rules natively in Rust" and "likely unnecessary unless you have a non-standard name").

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands (npx @oxlint/migrate, npm install -D oxlint, npx oxlint src/), JSON config blocks, and option/CLI mapping tables that cover the common migration cases.

5 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced with review checkpoints (review generated config, run --details to check unmigrated rules), but there is no explicit validate→fix→retry feedback loop, leaving minor validation gaps.

4 / 5

Progressive Disclosure

Well-organized into clearly signaled sections with a References list of external doc links, but at ~190 lines with no bundle files some reference material (plugin mapping table, full option list) is inlined that could live in a separate file.

4 / 5

Total

17

/

20

Passed

Description

90%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 strong: it clearly states what the skill does and gives explicit, natural trigger phrases with synonym coverage. Its only limitation is specificity, since it names one core action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and one core action ("migrating a project from ESLint to Oxlint"), but the trigger verbs migrate/convert/switch are synonyms of that single action rather than distinct concrete capabilities, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Explicitly answers both what ("Guide for migrating a project from ESLint to Oxlint") and when ("Use when asked to migrate, convert, or switch...") with concrete trigger phrases in third person, matching the top anchor.

5 / 5

Trigger Term Quality

Covers natural terms a user would say — migrate, convert, switch (synonyms), ESLint, Oxlint, linter, JavaScript/TypeScript — comprehensively including synonyms, matching the highest anchor.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (ESLint→Oxlint migration) with distinct, specific triggers and minimal overlap with other skills.

5 / 5

Total

18

/

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.