CtrlK
BlogDocsLog inGet started
Tessl Logo

chatto-pr-checklist

Pre-merge PR checklist for the Chatto codebase. Contains instructions for tasks that must run before a PR is merged. This skill should automatically run when a PR is opened.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

78%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 well-structured, actionable pre-merge checklist with an explicit verification step and clean sectioning. It is concise and appropriately organized, with only minor over-explanation in the intro and a few small validation gaps.

Suggestions

Trim the opening output-formatting paragraph to one sentence (e.g. 'Output only actionable items; omit areas needing no action.') to push conciseness toward 5.

Add an explicit final verification step in 'When you're done' (e.g. re-run the checklist items to confirm none remain open before pushing) to strengthen workflow_clarity.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence, with concrete instructions rather than concept explanations. The opening paragraph ('Please make sure to only output actionable items; if one area does not require further action, don't say so, just omit it. The user should receive a list of actionable todos.') is mildly over-explained and could be trimmed, keeping it just below the fully lean score-5 anchor.

4 / 5

Actionability

It gives concrete, specific guidance — named required PR-body sections (Why / What changed / Test plan), a concrete tool to invoke ('use `chatto-api-compatibility`'), a required label ('api-breaking-change'), and Conventional Commit syntax. As an instruction-only skill it has no code, but the guidance is actionable; minor gaps (e.g. no exact command for reading the body back from GitHub) keep it at 4 rather than 5.

4 / 5

Workflow Clarity

There is a clear sequenced checklist (familiarize → fill test gaps → update ADRs/docs → PR body → breaking-change classification → push) and an explicit verification checkpoint ('read the stored body back from GitHub and confirm it accurately represents the full diff'). Minor validation gaps elsewhere (e.g. no explicit re-check after fixing test gaps) prevent a 5.

4 / 5

Progressive Disclosure

This is a single-file, sub-50-line, single-purpose skill with no bundle files (references/scripts/assets absent) and clear section headers (PR Body Quality, Breaking Changes Checklist, When you're done). Per the simple-skill scoring note, well-organized sections alone warrant a 5 here.

5 / 5

Total

17

/

20

Passed

Description

78%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 both what the skill does and when it triggers, with good natural trigger terms and codebase-scoped distinctiveness. Its main weakness is specificity — it describes the skill as a checklist of tasks without naming the concrete tasks themselves.

Suggestions

Name 2-3 concrete checklist tasks in the description (e.g. 'reviews test coverage gaps, verifies ADR/docs updates, checks API compatibility') to lift specificity from 3 toward 4-5.

Add a natural synonym such as 'pull request' alongside 'PR' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Pre-merge PR checklist for the Chatto codebase') and one concrete action framing ('tasks that must run before a PR is merged'), but it does not enumerate the specific tasks, so coverage is not comprehensive. It is above score 2 (which only names a domain with minimal actions) but below 4, which expects several specific actions listed.

3 / 5

Completeness

It explicitly answers both 'what' ('Pre-merge PR checklist... Contains instructions for tasks that must run before a PR is merged') and 'when' ('This skill should automatically run when a PR is opened') with a concrete trigger phrase. The 'when' clause is explicit and concrete, matching the score-5 anchor; it is not the weaker/implied-when case of score 4.

5 / 5

Trigger Term Quality

It includes natural user-facing terms — 'PR', 'pre-merge', 'checklist', 'merge', 'when a PR is opened' — that a user would plausibly say. A few common synonyms (e.g. 'pull request', 'review') are missing, so it stops short of the comprehensive synonym coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

Scoping to 'the Chatto codebase' gives it a clear niche and low conflict risk with unrelated skills, though the generic 'PR checklist' concept could still overlap with other review/merge-related skills. It is mostly distinct with minor overlap risk rather than the fully clear niche of score 5.

4 / 5

Total

16

/

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.