chatto-release-notes

Create or update Chatto release pages from release-please state, tags, changelog entries, and PRs.

Quality

66%

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

Fix and improve this skill with Tessl

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

Quality

Content

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

The body is a lean, highly actionable set of rules with specific paths, components, props, and a verification command, organized into a clear topic sequence. It falls just short of top marks because it lacks a full MDX page example, an explicit fix-and-retry loop, and any bundle-file progressive disclosure.

Suggestions

Add a short complete MDX page skeleton showing ReleaseHero, ReleaseFeatureGrid with cards, Upgrade Notes, and the GitHub release link in order.

Make the verification feedback loop explicit, e.g. "If the build fails, fix the MDX and re-run until it passes."

Extract the per-component prop reference into a reference file and link to it from the Page And Components section to lighten the main body.

Dimension	Reasoning	Score
Conciseness	The body is dense imperative guidance with no padding about what release-please or MDX is, e.g. "Write one docs-website MDX page per stable minor release"; it earns a 4 rather than 5 because a few rules about what not to put in cards are slightly redundant.	4 / 5
Actionability	Concrete, executable specifics are given throughout — exact page path `apps/docs-website/src/content/docs/releases/<version-with-hyphens>.mdx`, component names and props (`ReleaseFeatureGrid`, `size="large"`, `status="Unreleased"`), and the build command `mise x -- pnpm --filter docs-website build`; not 5 because no complete copy-paste MDX page example is provided.	4 / 5
Workflow Clarity	Sections sequence the work (evidence → existing text → content → components → images → verification) and the Verification section supplies a concrete build command plus checks; not 5 because the fix-and-retry feedback loop is implicit rather than explicit, and the sequence is implied by section order rather than numbered.	4 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections with signposted references to real repo paths (AGENTS.md, the components directory); no bundle files exist to navigate and all content stays appropriately inline, so it fits the 4 anchor rather than 5 which expects one-level-deep reference files.	4 / 5
	Total	16 / 20 Passed

Description

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

The description clearly states what the skill does and is product-specific, but it omits any explicit "Use when..." trigger guidance and lacks natural synonyms such as "release notes", weakening completeness and trigger-term quality. It is a solid, specific description held back by the missing use-trigger clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when preparing or updating a Chatto release page for a new minor release."

Include natural user-facing synonyms like "release notes" and "version page" alongside "release pages".

Mention the stable-vs-prerelease distinction in the description so the trigger is more specific.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ("Create or update Chatto release pages") plus four specific data sources ("release-please state, tags, changelog entries, and PRs"), giving several specific actions with only minor coverage gaps — fits the 4 anchor and not 5 because the actions collapse to two verbs rather than multiple distinct operations.	4 / 5
Completeness	The "what" is clear ("Create or update Chatto release pages from release-please state, tags, changelog entries, and PRs") but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Relevant terms like "release pages", "changelog entries", and "PRs" appear, but common natural synonyms users would say (e.g. "release notes", "version page") are missing, matching the 3 anchor and not 4 which expects fuller keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The Chatto product niche plus the release-please-specific trigger make it mostly distinct with minimal conflict risk; not 5 because the absent "when" guidance leaves minor overlap with general docs/release skills.	4 / 5
	Total	14 / 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-notes/SKILL.md
Commit: 5cbd584

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.