chatto-release-checklist

Run before making a new Chatto release. Compares the candidate version with stable and prerelease baselines, writes a developer checklist and separate user-facing announcement to .context/, and reports API changes separately.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%

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-sequenced release-review workflow with concrete commands, exact paths, and complete templates, and no unnecessary concept explanation. Its main limitation is that all content lives inline in one long file with no progressive disclosure to deeper reference materials.

Suggestions

Move the large 'Developer Checklist Format' and 'Announcement Format' template blocks into reference files (e.g. references/checklist-template.md) and link to them from SKILL.md to slim the overview.

Consider extracting the API-surface path lists into a reference table so the proto/ConnectRPC/realtime paths are maintained in one place rather than repeated across the inputs and API-review sections.

Dimension	Reasoning	Score
Conciseness	Lean and operational throughout — concrete commands, file paths, and copy-paste templates with no concept-bloat (no explanations of what a release, protobuf, or release-please is). The length reflects genuine domain complexity, and nearly every token is actionable.	3 / 3
Actionability	Provides executable gh/git/jq commands, exact proto and source paths to diff, precise output file paths ('.context/release-checklist-<version>.md'), and complete fill-in templates for both the checklist and the announcement.	3 / 3
Workflow Clarity	Six numbered workflow steps are clearly sequenced with explicit decision checkpoints ('If a newer stable tag already exists, stop and ask the user how to proceed') and a follow-up checklist; the workflow is explicitly read-only so destructive-operation validation caps do not apply.	3 / 3
Progressive Disclosure	Well-organized into clear sections but it is a 209-line monolithic file with ~90 lines of inline template blocks and no external reference files or one-level-deep navigation; the checklist/announcement templates could be split out for a leaner overview.	2 / 3
	Total	11 / 12 Passed

Description

85%

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 specific, well-scoped description that states concrete actions and an explicit run-condition in third person. It is strong overall; its only weakness is narrow trigger-term coverage relying on a single 'making a new release' phrase.

Suggestions

Broaden trigger terms, e.g. 'Use when preparing, reviewing, or announcing a new Chatto release' to catch 'announce', 'publish', and 'prepare' phrasings.

Consider naming the deliverables in trigger language ('developer checklist', 'release announcement') so users asking for those outputs match this skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Compares the candidate version with stable and prerelease baselines, writes a developer checklist and separate user-facing announcement to .context/, and reports API changes separately' — each is a distinct, specific operation.	3 / 3
Completeness	Clearly answers what (compare versions, write checklist, write announcement, report API changes) and when ('Run before making a new Chatto release'), with explicit trigger guidance equivalent to a 'Use when' clause.	3 / 3
Trigger Term Quality	The single trigger phrase 'Run before making a new Chatto release' captures the core event but misses common variations users might say ('announce a release', 'publish a release', 'prepare a release').	2 / 3
Distinctiveness Conflict Risk	The Chatto-specific release niche ('new Chatto release', '.context/', API-change reporting) is highly specific and unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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: chattocorp/chatto
Path: .agents/skills/chatto-release-checklist/SKILL.md
Commit: 65f65c3

Reviewed: 5 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.