CtrlK
BlogDocsLog inGet started
Tessl Logo

changeset

Use this skill when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit `.changeset/*.md` release-note text. Do not use for implementation details or PR descriptions.

75

Quality

93%

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

93%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 tight, highly actionable skill body that sequences the changeset workflow clearly and points to canonical external docs rather than duplicating them. The only minor gap is the lack of an explicit feedback loop around the review checklist.

DimensionReasoningScore

Conciseness

Lean and token-efficient: it points to canonical repo docs ("`CONTRIBUTING.md` is canonical for...") instead of re-explaining concepts, and every section earns its place (e.g. the nursery-rule exception is Biome-specific knowledge Claude lacks).

5 / 5

Actionability

Fully executable guidance — copy-paste `just new-changeset-empty` command, a concrete frontmatter block (`"@biomejs/biome": patch`), a change→level→branch table, and specific heading-level (`####`/`#####`) and prose rules.

5 / 5

Workflow Clarity

Clear sequenced workflow (Decide → Choose Level → Create → Write → Review Checklist) with an explicit 7-item validation checklist, but no explicit "if a checklist item fails, fix and re-verify" feedback loop.

4 / 5

Progressive Disclosure

A concise self-contained overview organized into clear sections, with a well-signaled one-level-deep References section (CONTRIBUTING.md, justfile, versioning URL) and no nested references or inlined content that belongs elsewhere.

5 / 5

Total

19

/

20

Passed

Description

92%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, specific description that clearly states what it does, when to trigger it, and when not to, with concrete file artifacts and a negative-use clause. Its only gap is a handful of missing natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "decide whether it needs a changeset, choose the release level, or create and edit `.changeset/*.md` release-note text" — covering the full changeset lifecycle comprehensively.

5 / 5

Completeness

Explicitly answers both what (decide/choose/create-edit) and when ("Use this skill when a Biome change may affect users"), plus a concrete negative trigger ("Do not use for implementation details or PR descriptions").

5 / 5

Trigger Term Quality

Good natural-term coverage ("changeset", "release level", "release-note", ".changeset/*.md", "PR descriptions") including a file extension, but a few synonyms like "changelog" or "version bump" are absent.

4 / 5

Distinctiveness Conflict Risk

Narrow niche (Biome changesets) with a distinct file artifact (`.changeset/*.md`) and explicit negative boundary guidance, giving minimal conflict risk.

5 / 5

Total

19

/

20

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.