CtrlK
BlogDocsLog inGet started
Tessl Logo

eslint-migrate-options

Use this skill when `biome migrate eslint` must preserve configurable ESLint rule options through source-option models, Biome conversions, typed rule variants, and migration fixtures. Do not use for generated severity-only mapping or general rule-option design.

68

Quality

83%

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

88%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.

A lean, expert-level instruction body: tightly written imperative guidance, exact codebase artifacts, a sequenced pipeline with validation checkpoints and a review checklist, plus executable test commands. The only structural improvement would be moving per-plugin option-model/conversion detail into reference files, and the only actionability gap is the absence of one worked code example.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and domain-specific throughout ("Preserve source nesting until conversion", "Copy a current analogous arm rather than relying on remembered struct fields") with no padding and no explanation of concepts Claude already knows — every token earns its place.

5 / 5

Actionability

Provides concrete file names, exact symbols (`migrate_eslint_rule()`, `RuleConf<T>`, `RuleFixConfiguration::WithOptions`), fixture paths, and copy-paste commands (`cargo test -p biome_cli migrate_eslint`). Minor gaps remain: no Rust snippet for a conversion or typed-variant arm, instead deferring to existing analogous code.

4 / 5

Workflow Clarity

Sections follow the declared four-part pipeline in order (preconditions → model → convert → typed variant → wire migration → tests), with explicit validation steps ("Run the focused migration tests and inspect adjacent snapshots", "Search the enum's matches after adding the variant") and a closing Review Checklist — a clear sequence with checkpoints and a checklist.

5 / 5

Progressive Disclosure

Well-sectioned single-file body with a clearly signaled References section pointing to real codebase paths; however, no bundle files exist and the ~130-line body keeps everything inline, so it falls short of anchor 5's cleanly split, reference-file structure (and exceeds the under-50-lines simple-skill carve-out).

4 / 5

Total

18

/

20

Passed

Description

78%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.

A highly targeted description with an explicit trigger clause, a what-statement, and a do-not-use boundary. Its main limitation is that capabilities are expressed as artifact nouns inside the when-clause rather than as concrete verb-led actions, which caps specificity and completeness just below the top anchors.

Suggestions

Lead with a verb-led capability statement (e.g., "Implements custom `biome migrate eslint` option preservation: models ESLint option types, converts them to Biome configuration, adds typed rule variants, and adds migration fixtures.") before the when-clause.

Add a couple of natural trigger synonyms users might say, such as "eslint config migration" or "migrate eslint rules with options", to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (`biome migrate eslint`) and several concrete components — "source-option models, Biome conversions, typed rule variants, and migration fixtures" — but these are artifacts rather than verb-first actions, leaving minor coverage gaps versus anchor 5's comprehensive action list.

4 / 5

Completeness

Both what and when are present: an explicit "Use this skill when `biome migrate eslint` must preserve…" trigger plus a "Do not use for…" boundary. However, the what is embedded inside the when-clause rather than stated as a standalone capability statement, keeping it just below anchor 5's fully explicit both-parts form.

4 / 5

Trigger Term Quality

Contains good natural keywords a maintainer would say — "biome migrate eslint", "preserve configurable ESLint rule options", "severity-only mapping" — but misses common variations such as "eslint config" or "migration" phrased generally, so a few natural terms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (custom option-preserving migration in the Biome codebase) with an explicit exclusion — "Do not use for generated severity-only mapping or general rule-option design" — minimizing the risk of triggering for the wrong skill.

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.

Validation — 16 / 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.