Content
92%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is an efficient, well-structured conventions document that adds only repo-specific knowledge and points to the right external locations (changeset config, per-package AGENTS.md). Its single weakness is the absence of a concrete changeset example showing the file format. As an instruction-only skill, the lack of code is not itself penalized.
Suggestions
Add a short example changeset (frontmatter with package name and bump type, one-paragraph body written from the consumer's perspective) so the common case of writing a changeset is fully covered.
Optionally state where the changeset filename convention comes from (e.g., that changeset filenames are arbitrary .md files under .changeset/) to remove the last ambiguity about file creation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence: it states that packages are 'versioned and released with changesets' in one line and spends the rest on repo-specific conventions ('Every sentence must apply to each package the changeset lists', 'Use at most one paragraph per changeset'). Every token carries information Claude could not infer, so the 'could be tightened' level below does not apply. | 5 / 5 |
Actionability | Guidance is concrete and directive — 'adds a changeset file under .changeset/', 'write a separate changeset for each package', 'check it before writing the changeset' — but there is no example of an actual changeset file (e.g., its frontmatter with package name and bump type), which is a minor gap against the anchor requiring specific examples to cover the common cases. It is not level 3 because nothing is vague or pseudocode; the directives are executable as written. | 4 / 5 |
Workflow Clarity | This is a simple, single-purpose skill and the single action is unambiguous, with an explicit ordering cue ('A package's own AGENTS.md can carry further conventions... check it before writing the changeset'). Writing a markdown changeset is neither destructive nor a batch operation, so the validation-cap guideline does not apply and the simple-skill exception holds. | 5 / 5 |
Progressive Disclosure | The skill is under 50 lines, needs no external reference files, and is well organized with a heading and bulleted conventions; the one pointer it does make ('The changeset configuration... lives in .changeset/config.json') is clearly signaled and one level deep, so the short-skill guideline for a top score is satisfied. | 5 / 5 |
Total | 19 / 20 Passed |