CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/biome-complete

Complete Biome toolchain guidance for real repository workflows. Use when users ask to configure biome.json, run lint or format commands, migrate from ESLint or Prettier, tune rule severity, fix formatter drift, or replace mixed ESLint+Prettier pipelines with Biome-only workflows.

71

Quality

89%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

77%

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

The body is actionable with a well-validated workflow, but loses points for command duplication between the workflow and Quick Commands and for referencing a references/ bundle that is absent from the skill package.

Suggestions

Consolidate the Quick Commands section: four of its commands duplicate the Deterministic Workflow, so either remove the duplicates or have Quick Commands cross-reference the workflow steps to eliminate the redundancy (conciseness).

Create the missing references/ files (config-biome-json.md, linting-rule-categories.md, formatter-options.md, migration-eslint-prettier.md) so the progressive-disclosure links actually resolve (progressive_disclosure).

If the deep detail is not needed, inline the essential config and migration guidance directly in SKILL.md and drop the dangling references rather than promising files that are absent (progressive_disclosure).

DimensionReasoningScore

Conciseness

Mostly efficient and free of concepts Claude already knows, but the Quick Commands section duplicates four commands already presented in the Deterministic Workflow (init, check ., check . --write, check . --error-on-warnings), so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands (e.g. 'bunx @biomejs/biome check . --write', 'bunx @biomejs/biome format . --write') with expected results, meeting the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

The Deterministic Workflow is a clearly sequenced six-step process with explicit **Verify:** checkpoints (steps 3, 4, 6) and an Error Recovery feedback loop (disable rule groups then re-enable one at a time), matching the validation-and-recovery anchor.

3 / 3

Progressive Disclosure

The References section is well-signaled and one-level-deep, but the four referenced files (config-biome-json.md, linting-rule-categories.md, formatter-options.md, migration-eslint-prettier.md) do not exist — no references/ directory is present in the bundle — so the disclosure links are broken rather than resolving to real materials.

2 / 3

Total

10

/

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.

The description is strong: third-person voice, concrete actions, explicit 'Use when' triggers, and a distinct Biome-specific niche that minimizes conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'configure biome.json, run lint or format commands, migrate from ESLint or Prettier, tune rule severity, fix formatter drift, or replace mixed ESLint+Prettier pipelines' — matching the anchor for enumerating specific concrete actions rather than vague language.

3 / 3

Completeness

States what it does ('Complete Biome toolchain guidance for real repository workflows') and gives an explicit 'Use when users ask to...' clause with multiple triggers, satisfying both the what and when with explicit triggers.

3 / 3

Trigger Term Quality

Uses natural phrases users would say ('configure biome.json', 'migrate from ESLint or Prettier', 'fix formatter drift') with good coverage of common variations, beyond the 'some relevant keywords' bar of 2.

3 / 3

Distinctiveness Conflict Risk

Targets a clear Biome-only niche with ESLint/Prettier migration triggers that are unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents