biome-linting

Analyze, fix, and validate Biome linting workflows. Use when JavaScript or TypeScript projects need Biome commands, diagnostics, safe fixes, or CI lint gates.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

77%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 concise, well-structured runbook with strong validation discipline, but it stays at the process level without concrete Biome commands and its progressive-disclosure pointers are misaligned with the actual bundle.

Suggestions

Add concrete, copy-paste-ready Biome commands (e.g. `biome check`, `biome lint --apply-safe`, `biome ci`) with example invocations tied to the workflow steps so the guidance is executable, not just procedural.

Align the Progressive Disclosure section with the actual bundle by naming references/contract.yaml, references/evals.yaml, and references/task-profile.json with a one-line purpose each, instead of pointing to a non-existent archived directory path.

Replace or augment the conversational Examples with at least one concrete command sequence showing diagnose -> safe-fix -> revalidate, mirroring the workflow.

Dimension	Reasoning	Score
Conciseness	Lean directive-style sections with no padding or explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Process guidance is specific (classify mode, inspect 2-3 surfaces, take smallest action) but lacks concrete executable Biome commands or flags; the Examples section shows conversational prompts rather than command sequences.	3 / 5
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints and a feedback loop ('Stop at the first failed gate', 'Rerun the relevant validation after fixes'), reinforced by a dedicated Validation section.	5 / 5
Progressive Disclosure	The body is well-sectioned, but the Progressive Disclosure path ('Infrastructure/references/deferred-skill-context/agent-ops-biome-linting/') does not match the actual bundle in references/ (contract.yaml, evals.yaml, task-profile.json), and those files are never named or linked.	3 / 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-formed description that clearly states capabilities and explicit trigger conditions for a distinct tool niche. The only gap is missing common synonyms and config-file references in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain ('Biome linting workflows') and several concrete actions ('Analyze, fix, and validate') covering the workflow phases, with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' ('Analyze, fix, and validate Biome linting workflows') and 'when' with a concrete 'Use when...' trigger clause.	5 / 5
Trigger Term Quality	Strong natural keywords ('Biome linting', 'diagnostics', 'safe fixes', 'CI lint gates', 'JavaScript or TypeScript projects') but missing common synonyms (lint, format, linter) and the biome.json config file extension.	4 / 5
Distinctiveness Conflict Risk	Names the Biome tool explicitly with tool-specific triggers (CI lint gates, JS/TS), giving a clear niche with minimal overlap risk against generic linting skills.	5 / 5
	Total	18 / 20 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Skills/agent-ops/biome-linting/SKILL.md
Commit: 2f91362

Reviewed: 1 day 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.