CtrlK
BlogDocsLog inGet started
Tessl Logo

lint-rule-development

Use this skill when creating or modifying Biome lint rules or assists, including analyzer queries, semantic bindings, rule state, code actions, fix safety, options, registration, and end-user rule rustdoc. Also load diagnostics-development for substantial message/advice design and testing-codegen for fixture or snapshot mechanics.

74

Quality

91%

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

90%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, highly actionable instruction skill with concrete commands, real API references, and a clear workflow backed by a review checklist. Validation is present but the fix-retry feedback loop could be more explicit, and cross-skill loads are not centralized.

Suggestions

Make the snapshot/test failure feedback loop explicit: e.g., 'If a snapshot mismatches, update the fixture or rule and re-run `just test-lintrule` until it passes.'

Centralize the cross-skill load directives (diagnostics-development, testing-codegen, syntax-text-handling, eslint-migrate-options, changeset) into a single 'Related skills' section so navigation is one glance.

Consider moving the detailed Options integration-point checklist and the Actions test list into a referenced file to keep the overview shorter and improve progressive disclosure.

DimensionReasoningScore

Conciseness

Dense and lean with no basic-concept padding; it assumes Claude's competence with Biome/Rust and points to the canonical guide ('Read only the sections relevant to the rule rather than loading the entire guide') instead of duplicating it.

5 / 5

Actionability

Provides copy-paste-ready commands ('just new-js-lintrule useMyRule', 'just test-lintrule', 'just gen-rules', 'just f', 'just l') alongside concrete API names (Ast<Node>, Semantic<Node>, run(), action(), FixKind::Safe, declare_lint_rule!) and exact file paths.

5 / 5

Workflow Clarity

A clear 6-step sequence plus an explicit Review Checklist and snapshot inspection as validation checkpoints, but the error-recovery feedback loop (snapshot fails -> fix -> re-run) is only lightly implied rather than spelled out.

4 / 5

Progressive Disclosure

Well-organized into clear sections with one-level-deep references to canonical docs and other skills, all clearly signaled; minor gaps because cross-skill loads are scattered through the body and some detail (Options integration points, Actions test list) is inlined rather than split out.

4 / 5

Total

18

/

20

Passed

Description

92%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, specific description that clearly states what the skill does and when to use it, with comprehensive coverage of the Biome lint-rule development domain. It is highly distinctive and uses appropriate third-person trigger phrasing; its only weak spot is jargon density slightly limiting natural trigger-term variety.

DimensionReasoningScore

Specificity

Enumerates many concrete actions — 'analyzer queries, semantic bindings, rule state, code actions, fix safety, options, registration, and end-user rule rustdoc' — giving comprehensive coverage of the lint-rule development domain.

5 / 5

Completeness

Explicitly answers both 'what' (creating/modifying lint rules and assists with enumerated subtasks) and 'when' ('Use this skill when creating or modifying Biome lint rules or assists'), plus routing guidance via the 'Also load...' clause.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'creating or modifying Biome lint rules or assists' are present, but the body leans on technical jargon (analyzer queries, semantic bindings, rustdoc) and omits common synonyms a user might naturally say.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and specific — Biome lint rules and assists — with distinct triggers and minimal overlap risk against unrelated skills.

5 / 5

Total

19

/

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.