biome-developer

General development best practices and common gotchas when working on Biome. Use for avoiding common mistakes, understanding Biome-specific patterns (AST, syntax nodes, string extraction, embedded languages), and learning technical tips.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/biome-developer/SKILL.md

Quality

Content

65%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 dense, highly actionable Biome development reference carried by strong executable code examples and concrete API guidance. It is weaker on conciseness (some repetition and inferable context) and on workflow clarity / progressive disclosure, since it is a long inline reference rather than a sequenced workflow or a split file structure.

Suggestions

Consolidate the duplicated string-allocation warnings: the 'String Extraction' DO/DON'T and the 'Common Mistakes to Avoid' section cover the same .to_string()/inner_string_text() ground — keep one authoritative location and cross-reference it.

Trim the Purpose and Prerequisites sections to only what Claude cannot infer (e.g. drop 'Basic familiarity with Rust') to tighten the token budget.

Consider moving the API reference tables (String/Text/Value Extraction) into a reference bundle file and summarizing them inline, which would improve progressive disclosure and shorten the main body.

Dimension	Reasoning	Score
Conciseness	Most content is genuinely Biome-internal knowledge Claude lacks (e.g. inner_string_text(), TokenText semantics, workspace vs path dev-dependencies) and earns its place, but the 430-line body repeats themes (string/text allocation warnings appear in both the String Extraction section and 'Common Mistakes to Avoid') and the Purpose/Prerequisites sections restate context Claude can infer.	2 / 3
Actionability	It provides complete, executable Rust code in consistent WRONG/CORRECT pairs plus concrete method tables (String/Text methods, Value Extraction Methods), giving copy-paste-ready guidance with specific API names and commands like 'just qt biome_html_parser'.	3 / 3
Workflow Clarity	This is a topic-organized reference rather than a sequenced multi-step process, so there is no real workflow to sequence; per-topic DO/DON'T/Example structure is clear, but there are no explicit validation checkpoints or feedback loops, and the content does not present an ordered procedure.	2 / 3
Progressive Disclosure	Cross-skill references are well-signaled and one level deep (doc-comments, testing-codegen, parser-development, CONTRIBUTING.md) and it explicitly delegates rather than duplicating, but no bundle files exist and the bulk of the API reference and examples live inline in a single long SKILL.md rather than being split into separate reference files.	2 / 3
	Total	9 / 12 Passed

Description

75%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 solid, third-person description that clearly states both purpose and explicit use-triggers for a well-scoped niche. Its main weakness is that the listed actions are abstract categories ('understanding', 'learning') rather than concrete operations.

Suggestions

Replace abstract gerund actions ('understanding... patterns', 'learning technical tips') with concrete verbs tied to outcomes, e.g. 'inspect AST nodes, extract string content without allocation, handle Vue/Svelte embedded syntax'.

Drop the generic opener 'General development best practices' or fold it into the Biome-specific framing so the first phrase already signals the niche.

Dimension	Reasoning	Score
Specificity	It names the domain (Biome development) and enumerates specific subject areas ('AST, syntax nodes, string extraction, embedded languages'), but the actions themselves are abstract gerunds ('avoiding common mistakes, understanding... patterns, learning technical tips') rather than concrete verbs like 'extract text' or 'fill forms'.	2 / 3
Completeness	It states both what it does ('development best practices and common gotchas when working on Biome') and an explicit when-to-use clause ('Use for avoiding common mistakes, understanding Biome-specific patterns...'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	It includes relevant niche terms a Biome contributor would reference ('Biome', 'AST', 'syntax nodes', 'embedded languages'), but the opening 'general development best practices' is generic and the terms are framed as capability listings rather than the natural phrases a user would utter when needing the skill.	2 / 3
Distinctiveness Conflict Risk	The Biome-specific scope anchored to concrete internal concerns (AST, syntax nodes, string extraction, embedded languages) carves a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: biomejs/biome
Path: .claude/skills/biome-developer/SKILL.md
Commit: c50a853

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.