CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chatto-api-compatibility

Review Chatto public API and protocol changes for compatibility, migration needs, and generated output.

Quality

78%

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-api-compatibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary lean, repo-specific review procedure: concrete classification taxonomy, a thoughtful checklist of behaviors schema comparison cannot verify, explicit validation commands, and clean one-level delegation to policy files. The only soft spots are the absence of explicit failure-handling after a breaking-check failure and exact command invocations being delegated rather than inlined.

DimensionReasoningScore

Conciseness

Every sentence is an instruction with zero concept explanation or padding ('Do not repeat these policies in the review' actively suppresses token waste). It matches anchor 5: lean, assumes Claude's competence, every token earns its place.

5 / 5

Actionability

The guidance is concrete and executable — named classification categories ('additive, behavioral, deprecated, or breaking'), an enumerated behavior checklist, and a named command ('Run Buf breaking checks and tests'). It is not 5 because exact Buf invocations and the release-policy details are delegated to AGENTS.md rather than given copy-paste ready; as an instruction-only skill this is only a minor gap, not a deficiency.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with an explicit validation step (run Buf breaking checks and tests) and a reporting checklist ('checks run, and unresolved risks'). It falls short of 5 only because there is no error-recovery loop stating what to do when a breaking check fails — reporting unresolved risks implies it but does not make the feedback loop explicit.

4 / 5

Progressive Disclosure

The ~30-line body is well organized with numbered steps, and every external pointer (root AGENTS.md, proto/AGENTS.md, ADR-045) is one level deep, clearly signaled, and annotated with its purpose. Per the rubric's simple-skill note, content under 50 lines with no bundle files needs only well-organized sections to score 5, and there is no nested referencing to penalize.

5 / 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.

A concise, domain-specific description that clearly states what the skill does, but it lacks any 'Use when...' trigger clause and omits the most natural trigger synonyms ('breaking changes', 'backward compatibility'). Adding explicit trigger guidance would raise both completeness and trigger-term quality.

Suggestions

Append a trigger clause, e.g. 'Use when reviewing Chatto PRs that touch public API or .proto files, or when the user mentions API compatibility, breaking changes, or migration.'

Include the natural synonyms 'breaking changes' and 'backward compatibility' in the description so it matches the phrasing users actually say.

Optionally mention the classification output (additive / behavioral / deprecated / breaking) to sharpen the 'what' and improve specificity.

DimensionReasoningScore

Specificity

The description names the domain ('Chatto public API and protocol changes') and several concrete review targets ('compatibility, migration needs, and generated output'). It falls short of 5 because the fuller scope (classification, breaking-change checks, generated clients) is only implied, and above 3 because more than 1-2 specific actions are listed.

4 / 5

Completeness

It clearly answers 'what' ('Review Chatto public API and protocol changes for compatibility, migration needs, and generated output') but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like 'public API', 'protocol changes', 'compatibility', and 'migration needs' are natural for this niche, but the phrases a user would most likely say — 'breaking changes', 'backward compatibility', 'proto' — are absent. Anchor 3 (relevant keywords, missing common variations or synonyms) fits better than anchor 4's 'a few natural terms missing'.

3 / 5

Distinctiveness Conflict Risk

'Chatto public API and protocol changes' carves out a clear niche tied to a named product with distinct technical triggers (API, protocol, migration), so conflict risk with other skills is minimal. It is not 4 because there is no meaningful overlap with closely related skills — the named product makes it unambiguous.

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-api-compatibility/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.