Name: changesets
Rating: 70.39999999999999 (1 reviews)
Author: cloudflare

changesets

Use when creating a changeset, preparing a release, or bumping versions. Covers which packages to reference, how to write user-facing changeset descriptions, the release automation flow, and the npm/Docker version sync requirement. (project)

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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 highly actionable, well-structured single-file skill with concrete templates, examples, and a checklist. The main improvements are removing the duplicated package-reference rule and adding an explicit validation feedback loop for the changeset-creation workflow.

Suggestions

Remove the near-duplicate 'Only reference @cloudflare/sandbox, never @repo/shared or @repo/sandbox-container' paragraph in 'Writing the Description' since it restates the Rules section verbatim.

Add an explicit validation feedback loop for changeset creation (e.g., 'If the pre-commit hook or CI check rejects the changeset because it lists an internal package, edit the file to list only @cloudflare/sandbox and re-run').

Consider whether the Release Automation and Version Synchronization detail belong in a separate reference file to keep the overview shorter, which would also strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Largely lean and project-specific without over-explaining concepts Claude already knows, but the rule 'Only reference @cloudflare/sandbox, never @repo/shared or @repo/sandbox-container' is stated near-verbatim in both the Rules and Writing the Description sections, a minor redundancy that could be trimmed.	4 / 5
Actionability	Provides a copy-paste-ready changeset file template, concrete bad/good description examples with code, specific file paths (.changeset/, .github/workflows/release.yml, packages/sandbox/src/version.ts, Dockerfile), explicit bump rules, and a verification checklist covering the common cases.	5 / 5
Workflow Clarity	The Release Automation section gives a clear 6-step numbered sequence and a closing checklist for verification, and notes CI/pre-commit enforcement, but there is no explicit Claude-facing validate→fix→retry feedback loop, leaving it just below the 5 anchor.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Creating a Changeset, Writing the Description, Release Automation, Version Synchronization, Checklist) with no nested references and cohesive self-contained content, but at ~81 lines it exceeds the under-50-line simple-skill threshold that would grant a clean 5.	4 / 5
	Total	17 / 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-structured description that clearly states both what the skill covers and when to use it, with natural trigger terms and a distinct niche. Minor room to sharpen the action list beyond topical coverage phrasing.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions and coverage areas ('creating a changeset, preparing a release, or bumping versions' plus package referencing, description writing, release flow, version sync), but the 'Covers...' framing is slightly more topical than the crisp action list of the 5 anchor.	4 / 5
Completeness	Explicitly answers both 'what' ('Covers which packages to reference, how to write user-facing changeset descriptions, the release automation flow, and the npm/Docker version sync requirement') and 'when' ('Use when creating a changeset, preparing a release, or bumping versions') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases users would actually say ('creating a changeset', 'preparing a release', 'bumping versions') with good keyword coverage, though a few synonyms/extensions are absent relative to the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche (changesets/releases for the @cloudflare/sandbox package) with distinct triggers and the '(project)' tag, giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: cloudflare/sandbox-sdk
Path: .agents/skills/changesets/SKILL.md
Commit: 6abf639

Reviewed: 3 days 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.