chatto-pr-checklist

Check a Chatto pull request before review or merge. Use when opening a PR or when asked to check one.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/chatto/chatto-pr-checklist/SKILL.md

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.

The content is a tight, well-structured checklist that respects Claude's intelligence and points to the right external artifacts without over-explaining. Its only real gap is that several checklist items stay slightly abstract, naming what to check without specifying how to verify it.

Suggestions

Make "Check tests" more concrete by specifying how to run/locate them (e.g. the test command or directory referenced in AGENTS.md).

Add an explicit pass/fail signal for the diff review, such as what counts as "needs action" versus acceptable, to sharpen the validation checkpoint.

Tighten the PR Description section by giving one short structural template instead of a list of points to cover.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding, no explanations of what a PR or diff is, and every line is an actionable instruction, so every token earns its place.	5 / 5
Actionability	Concrete guidance references specific artifacts (root `AGENTS.md`, the `chatto-api-compatibility` skill link) and tells Claude exactly what to verify, but a few items like "Check tests" and "Explain the problem" stay high-level without naming specific commands or locations, leaving minor gaps.	4 / 5
Workflow Clarity	The checklist lays out a rough sequence (diff → tests → docs → API compat → commit/PR conventions → PR description) and includes a validation checkpoint ("read its stored description and check that it matches the complete diff"), but most steps lack explicit pass/fail criteria, keeping it just below fully explicit.	4 / 5
Progressive Disclosure	A short (under 50 lines) single-purpose skill with well-organized sections and one-level-deep references to `AGENTS.md` and a sibling skill — no nested references and easy to navigate, meeting the simple-skill exception for a top score.	5 / 5
	Total	18 / 20 Passed

Description

73%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 concise, third-person, and clearly states both what the skill does and when to use it, with project-specific triggers that make it distinct. Its main weakness is limited specificity — it describes a single check rather than enumerating the concrete checks the skill performs.

Suggestions

Expand the description to list 2-3 concrete checks (e.g. "Verify tests, docs, and API compatibility") so the what is more specific and comprehensive.

Add a natural synonym trigger such as "reviewing" or "merging a Chatto PR" to broaden keyword coverage.

Consider mentioning the companion chatto-api-compatibility skill in the description to clarify scope boundaries.

Dimension	Reasoning	Score
Specificity	Names the domain ("Chatto pull request") and one concrete action ("Check ... before review or merge"), but offers only a single action and no comprehensive list of checks, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	Explicitly answers both what ("Check a Chatto pull request before review or merge") and when ("Use when opening a PR or when asked to check one"), but the "what" is a single action rather than a concrete multi-part capability, so it stops short of a 5.	4 / 5
Trigger Term Quality	Includes natural phrases a user would say — "opening a PR" and "asked to check one" — giving good keyword coverage, though a few synonyms (e.g. "review a PR", "merge") are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scoped to the named Chatto project with PR-specific triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: chattocorp/chatto
Path: .agents/skills/chatto/chatto-pr-checklist/SKILL.md
Commit: 5cbd584

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.