CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chatto-pr-checklist

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

Quality

81%

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

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 body is an exemplary lean checklist: every line is non-obvious project-specific instruction, detail is delegated to clearly linked sibling skills and repo documents, and an explicit validation step closes the workflow. The only shortfall is that a few steps (e.g. how to obtain the diff) rely on the referenced materials rather than being spelled out inline.

DimensionReasoningScore

Conciseness

The body is a lean checklist where every line carries project-specific instruction Claude could not infer (Sweet notes policy, AGENTS.md doc records, scope limits). There is no padding and no explanation of already-known concepts, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Guidance is concrete throughout: named targets (root `AGENTS.md`, CONTRIBUTING.md#writing-change-notes), named sibling skills per change type, and an explicit scope boundary ('This checklist does not authorize changes to agent instructions, branch names, or remote repositories'). Minor gaps — e.g. no command for producing the branch diff — keep it below the fully executable anchor 5.

4 / 5

Workflow Clarity

The checklist reads in a coherent order (diff, tests, docs, change notes, code/API/frontend review, commit conventions, PR description) and includes an explicit validation checkpoint: 'After creating or updating a PR, read its stored description and check that it matches the complete diff.' It lacks feedback loops for failing individual checks, so it does not reach anchor 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, well organized into a checklist plus a PR Description section, and pushes all detail to clearly signaled one-level-deep links (sibling skill SKILL.md files, CONTRIBUTING.md, AGENTS.md) with no nested reference chains. This matches both the anchor-5 structure and the rubric's simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

70%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/imperative, and cleanly answers both what the skill does and when to use it with explicit trigger phrasing. Its main weakness is that 'check' is the only action verb, leaving the actual scope of the checklist unspecified and creating mild overlap with sibling Chatto review skills.

Suggestions

Enumerate the core checks in the description (e.g. tests, docs, change notes, code review) so the 'what' reflects the checklist's actual scope, not just the single verb 'check'.

Add a trigger variant for the pre-merge moment (e.g. 'or before merging a Chatto PR') to sharpen distinctiveness against the sibling chatto-release-checklist and chatto-code-review skills.

DimensionReasoningScore

Specificity

"Check a Chatto pull request before review or merge" names the domain and one concrete action but does not enumerate what the check covers (tests, docs, change notes, code review). It matches anchor 3 (domain and 1-2 concrete actions, not comprehensive) rather than 4, which requires several specific actions.

3 / 5

Completeness

Both parts are explicit: the what ("Check a Chatto pull request before review or merge") and the when ("Use when opening a PR or when asked to check one") with concrete trigger phrases. The 'what' is thin — 'check' alone doesn't state what the check involves — keeping it below anchor 5.

4 / 5

Trigger Term Quality

Natural terms users would say are present: "pull request", "PR", "review", "merge", "check", "opening a PR". A few common variations (e.g. "pre-merge check", "review this PR") are missing, so it falls just short of the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The "Chatto" scoping creates a clear niche that would not trigger generic skills, and the voice is appropriately imperative. Minor overlap risk remains with closely related sibling skills (e.g. release PRs also match this trigger while chatto-release-checklist exists), so it is not the minimal-conflict anchor 5.

4 / 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: 5 suspicious

Warning

Total

15

/

16

Passed

Repository

chattocorp/chatto

Path

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