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

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

Highly actionable and clearly sequenced content with strong validation checkpoints, scoring near the top on actionability and workflow clarity. The main weakness is progressive disclosure: everything is inlined in one long file with no reference files, where the output templates and API-surface lists could be split out.

Suggestions

Move the full Developer Checklist Format and Announcement Format templates into reference files (e.g. references/checklist-template.md, references/announcement-template.md) and link to them from SKILL.md to reduce inline bulk.

Extract the per-surface API inspection path lists (proto/chatto/..., cli/internal/..., packages/..., apps/...) into a reference doc, keeping only the decision rules inline.

Add a short 'Quick start' summary at the top so the core flow is graspable before the detailed steps and templates.

Dimension	Reasoning	Score
Conciseness	The body is dense but almost every line is repo-specific, actionable guidance (exact paths, commands, classifications) rather than concepts Claude already knows; minor trimming is possible in the two full output templates, keeping it just below a 5.	4 / 5
Actionability	Provides fully executable commands (gh, git, jq with concrete flags), exact file paths under proto/cli/packages/apps, and complete copy-paste markdown templates for both output files — covering the common cases comprehensively.	5 / 5
Workflow Clarity	A clearly sequenced six-step workflow with explicit stop-gates ('stop and ask the user'), source-freshness recording, a dedicated Follow-Up Checklist with verification checkboxes, and classification guidance — matching the top anchor's validation and feedback-loop criteria.	5 / 5
Progressive Disclosure	Sections are well-organized, but the 210-line body inlines two full output templates and all reference material in a single SKILL.md with no bundle files or one-level-deep references, so content that could live in separate files is inline.	3 / 5
	Total	17 / 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, concrete description that clearly states both what the skill does and when to use it, scoped to a distinct niche. The only minor gap is keyword variety — it leans on 'release' without synonyms like publish, ship, or changelog.

Suggestions

Add natural synonyms such as 'publish', 'ship', 'cut a release', or 'changelog' to broaden trigger-term coverage.

Consider naming the output artifacts in trigger phrasing (e.g. 'Use when preparing a Chatto release announcement or release checklist') to strengthen the when-clause.

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' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what (compare versions, write checklist + announcement, report API changes) and when ('Run before making a new Chatto release') with a concrete trigger phrase, matching the top anchor.	5 / 5
Trigger Term Quality	'Run before making a new Chatto release' gives good coverage of the natural term 'release', but common synonyms like 'publish', 'ship', 'cut a release', or 'changelog' are missing, so it is not a full 5.	4 / 5
Distinctiveness Conflict Risk	The 'Chatto release' niche with API-change and announcement specifics is highly specific and unlikely to trigger for unrelated skills, matching the clear-niche anchor.	5 / 5
	Total	19 / 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: chattocorp/chatto
Path: .agents/skills/chatto-release-checklist/SKILL.md
Commit: 967a9a1

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.