chatto-release-notes

Create or update Chatto docs website release pages by comparing release-please state, tags, commits, changelog entries, and PRs

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/chatto-release-notes/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear, validated workflow and concrete commands, but it is a long monolithic document whose repeated rules and detailed conventions could be tightened or split into reference files for better token efficiency and progressive disclosure.

Suggestions

Tighten repeated rules — several placement rules (what stays out of feature grids, upgrade-notes vs feature card) appear in both the Audience and Page Structure sections; consolidate to a single authoritative list.

Split the detailed component/wording conventions into a reference file (e.g. RELEASE_CONVENTIONS.md) and keep SKILL.md as a lean overview with a one-level-deep pointer.

Move the time-sensitive version examples (0.4.0, 0.3.8, beta suffixes) into a clearly bounded 'examples' or 'old patterns' note so they do not penalize conciseness as they age.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence, but it is long and repeats several rules (e.g., upgrade-notes placement, what stays out of feature grids) across sections, which could be tightened.	2 / 3
Actionability	It provides concrete, executable commands (jq/git/gh invocations, mise build) and complete MDX/MDX-frontmatter code blocks that are copy-paste ready, matching the fully-executable anchor.	3 / 3
Workflow Clarity	A clear sequenced workflow (find target release, check existing page, research range, assemble page, build/verify) with explicit validation checkpoints ('Do not claim full verification if only the build ran') and error-recovery guidance ('If the computed target is not clear, stop and explain').	3 / 3
Progressive Disclosure	The skill is a single SKILL.md with no bundle files and well-organized sections, but it is a monolithic block of detailed rules (~400 lines) with content that could be split into reference files, so it is not a lean overview pointing one level deep.	2 / 3
	Total	10 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and clearly scoped to a distinct niche, but it omits an explicit 'Use when...' trigger clause, which caps completeness and leaves natural user phrasings partly uncovered.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers such as 'Use when creating or updating Chatto release notes, changelog pages, or docs-website release pages.'

Include common user phrasings like 'release notes' and 'changelog' so the trigger terms match what users actually say.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Create or update Chatto docs website release pages' by 'comparing release-please state, tags, commits, changelog entries, and PRs' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	It states clearly what the skill does but gives no explicit 'Use when...' trigger clause, so the 'when' side is only implied and completeness is capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	It mentions domain terms (release pages, release-please, tags, commits, changelog, PRs) but omits the natural phrasings a user would say ('release notes', 'changelog', 'docs site') and has no 'Use when...' trigger list, leaving common variations uncovered.	2 / 3
Distinctiveness Conflict Risk	The very specific scope (Chatto docs website release pages built from release-please state) carves a clear niche unlikely to trigger for any other skill.	3 / 3
	Total	10 / 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-notes/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.