CtrlK
BlogDocsLog inGet started
Tessl Logo

chatto-api-compatibility

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

60

Quality

70%

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

Quality

Content

82%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 tight, well-sequenced review workflow with concrete directives and a verification step, appropriately deferring policy detail to external repo docs. The main gap is the absence of an explicit failure-feedback loop and concrete command examples.

DimensionReasoningScore

Conciseness

The body is lean and directive ("Read root AGENTS.md for the current release policy", "Run Buf breaking checks and tests"), assumes Claude's competence, and contains no concept-padding or unnecessary explanation.

5 / 5

Actionability

Gives concrete, specific guidance — a change taxonomy (additive/behavioral/deprecated/breaking), an explicit behavioral-check list (authorization, errors, pagination, cursors, retries, realtime), and a named tool (Buf) — but offers no copy-paste commands or examples.

4 / 5

Workflow Clarity

A clear numbered 1–5 sequence with a verification checkpoint ("Run Buf breaking checks and tests", "A passing schema check does not prove behavioral compatibility"), but no explicit fix→re-validate feedback loop on check failure.

4 / 5

Progressive Disclosure

Short, well-organized body with clearly signaled one-level-deep references (root AGENTS.md, proto/AGENTS.md, ADR-045); no bundle files exist, so structure is scored on the body alone, which is appropriately split between orientation and the numbered workflow.

4 / 5

Total

17

/

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 targets a distinct Chatto-specific niche, but it omits any "when to use" trigger guidance and relies on a narrow set of domain keywords. Adding an explicit trigger clause and synonyms would raise completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when reviewing Chatto API or protocol changes, planning migrations, or validating generated clients.'

Broaden trigger terms with natural synonyms and artifacts users mention, such as 'breaking changes', 'proto changes', '.proto files', 'generated SDKs', or 'release notes'.

Consider listing the concrete deliverables (classification of changes, migration actions, risk report) to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ("Chatto public API and protocol changes") and three concrete review actions ("compatibility, migration needs, and generated output"), but coverage is framed around a single review verb rather than a comprehensive action list.

4 / 5

Completeness

The "what" is clear (review API/protocol changes for compatibility, migration, output), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ("public API", "protocol changes", "compatibility", "migration") but lacks natural synonyms and file extensions a user might actually say.

3 / 5

Distinctiveness Conflict Risk

The Chatto-specific framing ("Chatto public API and protocol changes") carves a distinct niche with minimal overlap risk, though no explicit trigger phrases reinforce the boundary.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

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.