CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

58

Quality

67%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./Skills/agent-ops/biome-linting/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads as a generic agent process template with 'Biome' inserted into the title and description. It lacks any concrete Biome-specific knowledge—no CLI commands, no configuration examples, no diagnostic patterns, no rule names, and no executable code. The workflow and constraints sections describe sound general practices but fail to teach Claude anything it doesn't already know about how to approach a linting task.

Suggestions

Add concrete Biome CLI commands with actual flags and examples, e.g., `biome check .`, `biome lint --apply src/`, `biome ci`, and show expected output patterns for common diagnostics.

Include a specific example workflow showing: a real Biome diagnostic message, the command to identify it, the safe fix command, and the validation rerun—not just abstract steps.

Replace generic agent behavior sections (Philosophy, Anti-Patterns, Constraints) with Biome-specific knowledge such as common rule categories, the difference between safe and unsafe fixes, and biome.json configuration patterns.

Add concrete CI integration examples showing exact commands for GitHub Actions or similar CI systems, since 'CI lint gates' is listed as a use case but no CI-specific guidance is provided.

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes several sections that are generic process boilerplate (Philosophy, Anti-Patterns, Constraints) rather than Biome-specific knowledge Claude doesn't already know. Sections like 'Avoid' and 'Constraints' contain general agent behavior guidance that adds little Biome-specific value.

2 / 3

Actionability

The skill contains no concrete Biome commands, no executable code examples, no specific CLI flags, and no actual diagnostic patterns. Everything is abstract guidance like 'Inspect 2-3 focused surfaces' and 'Take the smallest action' without showing what a Biome command actually looks like (e.g., `biome check`, `biome lint --apply`, `biome ci`).

1 / 3

Workflow Clarity

The workflow has a numbered sequence and mentions validation/rerun steps, and the Validation section includes a fail-fast pattern. However, the steps are abstract ('Classify the requested mode', 'Inspect 2-3 focused surfaces') with no concrete Biome-specific checkpoints, commands, or examples of what validation looks like in practice.

2 / 3

Progressive Disclosure

The skill references a deferred context directory (`Infrastructure/references/deferred-skill-context/agent-ops-biome-linting/`) and instructs to load only what's needed, which is good structure. However, no bundle files are provided to verify these references exist, and the main content lacks the concrete Biome-specific material that should be present at the top level before deferring to references.

2 / 3

Total

7

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description that concisely covers what the skill does and when to use it. It uses third person voice, includes specific Biome-related trigger terms, and has a clear 'Use when' clause with natural language triggers. The description is distinctive enough to avoid conflicts with other linting or code quality skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Analyze, fix, and validate Biome linting workflows' along with specific capabilities like 'Biome commands, diagnostics, safe fixes, or CI lint gates'.

3 / 3

Completeness

Clearly answers both what ('Analyze, fix, and validate Biome linting workflows') and when ('Use when JavaScript or TypeScript projects need Biome commands, diagnostics, safe fixes, or CI lint gates') with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'Biome', 'linting', 'JavaScript', 'TypeScript', 'diagnostics', 'safe fixes', 'CI lint gates'. These cover the key terms a user working with Biome would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive by specifying 'Biome' as the tool, which clearly differentiates it from ESLint, Prettier, or other linting skills. The combination of Biome-specific terms like 'safe fixes' and 'CI lint gates' makes conflicts unlikely.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

10

/

11

Passed

Repository
jscraik/Agent-Skills
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.