CtrlK
BlogDocsLog inGet started
Tessl Logo

eslint-migrate-options

Guide for implementing ESLint-to-Biome rule option migrators inside `biome migrate eslint`. Use whenever you add or update a Biome lint rule that has an ESLint source rule with configurable options, need to deserialize plugin-specific ESLint options, or need custom migration logic beyond the auto-generated severity mapping.

75

Quality

92%

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

85%Weight 40%Scale 1-3

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 guide with concrete code patterns and explicit validation feedback loops tailored to a genuinely complex codebase task. Its only weakness is mild verbosity from duplicated configuration-type code blocks that could be consolidated.

Suggestions

Collapse the fixable and non-fixable `migrate_eslint_rule()` examples into one block with a short note on the single `RuleConfiguration` vs `RuleFixConfiguration` difference, to remove near-duplicate code.

Trim conversational step intros (e.g. 'This saves time and helps match the patterns already used in migrate_eslint_rule()') since the actionable instruction already precedes them.

Consider moving the worked `numeric-separators-style` example into a reference file and linking it, keeping SKILL.md focused on the workflow steps.

DimensionReasoningScore

Conciseness

The body is dense and assumes Biome/Rust competence without re-explaining basics, but it carries redundancy — the near-identical fixable and non-fixable Rust blocks and a few chatty step intros ('This saves time and helps match the patterns') could be tightened without losing clarity.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance throughout — concrete Rust structs, `From` impls, `Rule` enum variants, match arms, `cargo check/test/insta` commands, and fixture instructions.

3 / 3

Workflow Clarity

A clearly sequenced 6-step workflow bookended by a 'Before You Edit' checklist and a 'Review Checklist', with explicit verification feedback loops (`cargo insta accept/reject`, `cargo test`) for the codegen/snapshot operations.

3 / 3

Progressive Disclosure

No bundle files exist, so the single SKILL.md is appropriately self-contained with well-organized sections; the References list points one level deep to codebase paths rather than nesting into other skill files.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 tight, third-person description that names the specific capability, gives multiple concrete sub-actions, and provides an explicit 'Use whenever...' trigger with several natural phrasings. It is both distinctive and complete.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'implementing ESLint-to-Biome rule option migrators', 'deserialize plugin-specific ESLint options', and 'custom migration logic beyond the auto-generated severity mapping' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Guide for implementing ESLint-to-Biome rule option migrators inside `biome migrate eslint`') and when ('Use whenever you add or update a Biome lint rule... or need custom migration logic beyond the auto-generated severity mapping').

3 / 3

Trigger Term Quality

Uses the natural terms a Biome contributor would say ('biome migrate eslint', 'ESLint source rule with configurable options', 'deserialize plugin-specific ESLint options') in third-person voice, with good coverage of phrasings.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (option migrators inside Biome's eslint migrate pipeline) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
biomejs/biome
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.