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

81%

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

75%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 well-structured, actionable migration guide that respects Claude's intelligence and provides concrete file/function/command anchors with a verification checklist. It could benefit from an explicit test-failure retry loop to fully close the workflow.

Suggestions

Add an explicit feedback loop in the Tests section: if a focused migration test fails, fix the conversion/option model and re-run the specific snapshot before proceeding.

Include one short worked example showing a source ESLint payload mapped through to the resulting RuleConf variant, to close the minor actionability gap.

Tighten abstract directive bullets like "Preserve source nesting until conversion" into concrete do/don't pairs referencing the actual deserializer contract.

DimensionReasoningScore

Conciseness

Lean and bullet-driven with no explanation of basic Biome/ESLint concepts; a few directive bullets (e.g. "Preserve source nesting until conversion") could be tightened, so it sits just below fully lean.

4 / 5

Actionability

Gives concrete file names, function names (migrate_eslint_rule, migrate_eslint_any_rule), enum variants (RuleConfiguration::WithOptions), method patterns (option_or_default, into_vec), and copy-paste cargo commands; minor gaps remain as no full worked code example is shown, appropriate for an instruction skill on an existing codebase.

4 / 5

Workflow Clarity

Clear sequence from Preconditions through Pipeline, modeling, conversion, typed variant, wiring, tests, and a Review Checklist, with validation via focused migration tests and snapshot inspection; lacks an explicit validate-fix-retry loop, keeping it below 5.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with a Key Files table and a References list pointing one level deep to repo paths and the ESLint docs URL; no bundle files exist, and the inline reference table is appropriate for the overview, with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

87%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 strong, well-scoped description that clearly states both capability and trigger conditions with explicit negative boundaries. Trigger terms are domain-appropriate, though slightly jargon-heavy without synonyms.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("preserve configurable ESLint rule options through source-option models, Biome conversions, typed rule variants, and migration fixtures"), but these are pipeline stages rather than fully concrete user-facing operations, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (preserve configurable ESLint rule options through the listed stages) and when ("Use this skill when `biome migrate eslint` must preserve...") with concrete trigger phrasing and a clear negative boundary.

5 / 5

Trigger Term Quality

Includes the natural command phrase a Biome contributor would say ("biome migrate eslint") plus "ESLint rule options" and "severity-only mapping"; a few synonyms or natural variations are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow (preserving configurable ESLint options during Biome migration) and the explicit "Do not use for generated severity-only mapping or general rule-option design" clause sharply separates it from adjacent skills, minimizing conflict risk.

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