CtrlK
BlogDocsLog inGet started
Tessl Logo

chatto-release-notes

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

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/chatto-release-notes/SKILL.md
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 content is a tightly written, highly actionable guide with concrete commands, exact paths, and a clear sequenced workflow that includes explicit validation. It loses only slightly on conciseness (some repeated anti-pattern rules) and progressive disclosure (no bundle files to split the long detail out).

Suggestions

Consolidate the repeated compatibility-only / implementation-only change exclusions (which appear across Audience, Page Structure, and Wording Rules) into a single canonical rule with back-references to reduce token weight.

Consider extracting the component prop reference and MDX templates into a bundled reference file under references/ so SKILL.md can stay a leaner overview.

DimensionReasoningScore

Conciseness

The body is dense, directive, and free of concept explanations Claude already knows, with nearly every line a specific rule, path, or command; minor repetition of compatibility-only-change rules across sections keeps it just short of a 5.

4 / 5

Actionability

Provides fully executable commands (git tag listing, gh pr view, mise/pnpm build), exact file paths, concrete MDX snippets, and exact component props covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

Clear end-to-end sequence (target release, existing-page safety, research/comparison, page structure, sidebar, verification) with an explicit validation checkpoint (docs build), an error-recovery halt ('stop and explain the ambiguity before writing files'), and a guard against overclaiming verification.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one-level-deep repo-path references and no nested references, but the skill is long and multi-step with no bundle files to offload detail, so it stays just below a 5.

4 / 5

Total

18

/

20

Passed

Description

66%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, but it omits an explicit 'Use when...' trigger clause, which caps its completeness score. Trigger term coverage is good but could be broadened with synonyms like 'release notes' or 'changelog'.

Suggestions

Add an explicit 'Use when ...' trigger clause, e.g. 'Use when the user asks to create or update Chatto release notes or docs release pages for an upcoming minor release.'

Broaden trigger terms to include natural synonyms such as 'release notes', 'changelog', and 'what's new' so it matches how users actually phrase the request.

DimensionReasoningScore

Specificity

Lists several specific actions ('Create or update', 'comparing release-please state, tags, commits, changelog entries, and PRs') with concrete inputs, though it centers on the comparison scope rather than enumerating the full set of actions performed on the page.

4 / 5

Completeness

Gives a clear 'what' but contains no explicit 'Use when...' trigger clause; the 'when' is only weakly implied, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural phrases like 'release pages', 'docs website', and 'release-please', but misses common synonyms a user might say such as 'release notes', 'changelog', or 'what's new'.

4 / 5

Distinctiveness Conflict Risk

The Chatto docs release-page niche is clearly scoped with distinct triggers, leaving only minor overlap risk with a generic docs or changelog skill.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
chattocorp/chatto
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.