CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chatto-release-notes

Create or update Chatto release pages from Sweet Release state, tags, changelog entries, and PRs.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

90%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 an exemplary instruction-style skill: lean, imperative, and packed with exact paths, commands, component names, and ordering rules that leave little ambiguity about what to produce. The only notable gaps are the implicit (rather than explicit) end-to-end process sequence with no build-failure recovery loop, and the absence of any content splitting despite the file's length.

DimensionReasoningScore

Conciseness

The body is dense, imperative, task-specific policy ("Omit internal refactors, test work, CI, and generated-file changes", "Use hyphens in filenames and dotted versions in visible text") with no explanation of concepts Claude already knows and only trivial internal restatement (card sizing appears in both the page-order list and the Cards section) — lean and every token earns its place.

5 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: exact paths ("apps/docs-website/src/content/docs/releases/<version-with-hyphens>.mdx"), an executable command ("mise x -- pnpm --filter docs-website build"), exact component names and props (ReleaseFeatureGrid, imageSrc, status="Unreleased"), a concrete URL pattern, and exact section headings and ordering — no pseudocode or vague direction.

5 / 5

Workflow Clarity

The evidence-gathering → release-determination → comparison → writing → build-verification flow is coherent, with an explicit stop checkpoint ("Stop and explain if the target release cannot be determined") and explicit validation ("Run mise x -- pnpm --filter docs-website build after page edits... Report which checks ran"). It falls short of 5 because the process sequence is implied by section order rather than explicitly ordered, and there is no error-recovery loop for a failed build.

4 / 5

Progressive Disclosure

Sections are well organized and external pointers are clearly signaled and one level deep (apps/docs-website/AGENTS.md, the release-notes components directory, the chatto-release-checklist skill), with no bundle files to structure. However, the >50-line detailed component/card/image specification is kept fully inline and could arguably be split into a reference file, leaving a minor organization gap versus the "content appropriately split" anchor.

4 / 5

Total

18

/

20

Passed

Description

62%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 is specific and clearly scoped to a distinct niche, with concrete actions and named data sources. Its main weaknesses are the complete absence of explicit "when to use" trigger guidance and the miss of the most natural trigger phrase ("release notes"), which the skill's name itself uses.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or updating Chatto release notes pages, or when the user mentions a Chatto release, version rollout, or changelog page."

Include the phrase "release notes" in the description, since users (and the skill name itself) say "release notes" far more often than "release pages".

Optionally mention the update-vs-create distinction's trigger context (e.g. "when a new stable minor release is being prepared") to sharpen the "when" half.

DimensionReasoningScore

Specificity

"Create or update Chatto release pages" names two concrete actions and enumerates four specific input sources ("Sweet Release state, tags, changelog entries, and PRs"), going beyond the 3-anchor's bare 1-2 actions, but coverage has minor gaps (no mention of verification or image handling), so it is not the comprehensive 5.

4 / 5

Completeness

The "what" is clear and concrete (create/update Chatto release pages from listed sources), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords are present ("release pages", "changelog", "tags", "PRs"), but the most natural user phrase — "release notes", the skill's own name — is absent and no synonyms or variations are covered, matching the anchor for missing common variations rather than good coverage.

3 / 5

Distinctiveness Conflict Risk

"Chatto release pages" combined with "Sweet Release state" defines a clear product-specific niche with distinct triggers and minimal conflict risk with any other skill, matching the 5 anchor; no neighboring anchor fits better.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

chattocorp/chatto

Path

.agents/skills/chatto-release-notes/SKILL.md

Reviewed

Table of Contents

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.