CtrlK
BlogDocsLog inGet started
Tessl Logo

changeset

Guide for creating and writing proper changesets for Biome PRs. Use when a PR introduces user-visible changes (bug fixes, new features, rule changes, formatter changes, parser changes) that need a changeset entry for the CHANGELOG. Trigger when creating changesets, writing changeset descriptions, or choosing the correct change type.

80

Quality

100%

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

100%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.

The content is lean, highly actionable, and well-structured with concrete commands and examples plus clear guardrails against invalid output. It respects token budget while remaining copy-paste ready.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — no preamble on what Biome or a changeset is — and every section delivers actionable guidance with no padded explanation, fitting the 'lean and efficient' anchor.

3 / 3

Actionability

Provides a concrete command ('just new-changeset-empty'), copy-paste changeset format blocks, and specific per-change-type writing examples, making guidance fully executable.

3 / 3

Workflow Clarity

Single-task skill with an unambiguous create→edit→choose-type→format sequence plus explicit guardrails ('Do not simply append... which creates an invalid changeset'; header levels 'break the CHANGELOG tooling'), satisfying the simple-skill allowance.

3 / 3

Progressive Disclosure

No bundle files exist; the skill is self-contained with well-organized sections and clearly-signaled external references (CONTRIBUTING.md, versioning page, changesets docs), so well-organized sections suffice.

3 / 3

Total

12

/

12

Passed

Description

100%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.

The description is specific, trigger-rich, and clearly distinguishes the skill's niche. It answers both what and when without verbosity or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'creating and writing proper changesets' plus an enumerated set of change types (bug fixes, new features, rule changes, formatter changes, parser changes) — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states both what (creating/writing changesets for the CHANGELOG) and when (two explicit trigger clauses), satisfying the 'clearly answers both what AND when' anchor.

3 / 3

Trigger Term Quality

'Use when a PR introduces user-visible changes' and 'Trigger when creating changesets, writing changeset descriptions, or choosing the correct change type' give good coverage of natural terms a contributor would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'Biome PRs' with changeset-specific triggers, giving it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.