CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chatto-release-checklist

Check Chatto release readiness, including release metadata, upgrade guidance, and docs website consistency. Use when preparing or reviewing a Chatto release or release PR.

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 lean checklist: dense, sequenced, with explicit validation checkpoints, defined report states, and well-signaled one-level references to repo docs and sibling skills. The only gaps are minor — a few checks omit the exact command or tool to run, and the docs-website detail could live in a reference file.

DimensionReasoningScore

Conciseness

The body is a dense checklist where nearly every line carries instruction ('Do not move published tags', 'fresh-install tests alone do not verify upgrades') with no explanation of concepts Claude already knows and no padding, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Guidance is largely executable: specific file paths ('apps/docs-website/src/content/docs/index.mdx', 'apps/docs-website/astro.config.mjs'), named constants, a runnable command ('mise x -- pnpm --filter docs-website build'), and enumerated artifact targets (GHCR, npm, Homebrew, TestFlight). A few checks such as 'Check required CI results for the release commit' do not name the specific command or tool, keeping it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The phases are clearly sequenced (Before Publication, Compatibility And Upgrades, Docs Website, After Publication, Verification And Report) with explicit validation checkpoints ('Run mise x -- pnpm --filter docs-website build after page edits', 'Verify changed navigation links in a local browser preview'), explicit pending semantics, and defined report states ('verified, pending, failed, or not applicable'), matching anchor 5.

5 / 5

Progressive Disclosure

Sections are well organized and all external references are well-signaled and one level deep ('[the release process](../../../docs/RELEASING.md)', '[chatto-release-notes](../chatto-release-notes/SKILL.md)', '[chatto-api-compatibility](../chatto-api-compatibility/SKILL.md)'). The Docs Website section carries substantial inline detail and the body exceeds the simple-skill threshold, so it sits at anchor 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Description

82%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 description with an explicit and concrete 'Use when' trigger clause, product-specific distinctiveness, and natural trigger phrases. Its only weakness is that the capability list relies on a single generic verb with enumerated topics rather than multiple distinct concrete actions.

DimensionReasoningScore

Specificity

The description names a clear domain ('Check Chatto release readiness') and enumerates three concrete coverage areas ('release metadata, upgrade guidance, and docs website consistency'), but all actions collapse into the single generic verb 'Check' and coverage areas like CI and artifact verification are only implied, matching anchor 3 rather than the several distinct concrete actions of anchor 4.

3 / 5

Completeness

It explicitly answers both questions: the 'what' ('Check Chatto release readiness, including release metadata, upgrade guidance, and docs website consistency') and a concrete 'when' ('Use when preparing or reviewing a Chatto release or release PR'), matching anchor 5; the 'when' clause is already fully explicit so anchor 4's caveat does not apply.

5 / 5

Trigger Term Quality

Phrases like 'preparing or reviewing a Chatto release or release PR' and 'release readiness' are natural terms a user would say, giving good keyword coverage; common synonyms such as 'version bump', 'changelog', or 'publishing' are missing, so it does not reach anchor 5.

4 / 5

Distinctiveness Conflict Risk

The product-specific 'Chatto' naming creates a clear niche with distinct triggers ('Chatto release', 'release PR'), making conflict with other skills minimal.

5 / 5

Total

17

/

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: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

chattocorp/chatto

Path

.agents/skills/chatto-release-checklist/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.