CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

check-pr

Waits for a PR's checks and reviews to finish, then reports the unresolved review threads, the failing checks and the gaps in the PR description. Use when the user asks to check a PR, whether a PR is ready, or what the Greptile review found.

Quality

80%

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

Fix and improve this skill with Tessl

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

Quality

Content

71%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 exceptionally lean, well-sequenced workflow with a concrete command, explicit polling and a done-when checkpoint, and a precise report format. Its main weakness is that every command and GraphQL query is delegated to ./queries.md, which is missing from the skill bundle, leaving the executable layer and the progressive-disclosure path broken; the ../../guidelines/pull-requests.md links also point outside the bundle and are unverifiable.

Suggestions

Ship queries.md alongside SKILL.md (or inline the GraphQL queries and gh commands): the body delegates all commands for steps 2–3 to ./queries.md, which does not exist in the bundle, so those steps cannot currently be executed.

Add an explicit timeout or fallback for the polling loop (e.g., what to do if a check stays pending indefinitely or Greptile never posts a review) to provide an error-recovery feedback loop.

Verify the out-of-bundle links (../../guidelines/pull-requests.md, ../handle-pr-comments/SKILL.md) resolve where the skill is installed, or inline the one-line ci:* label rule they are cited for.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and efficient with zero padding: no concept explanations (it assumes Claude knows gh and GraphQL), and every line instructs ("Poll `statusCheckRollup` every 30 seconds", "Put human comments before bot comments"). The one explanatory clause — "because only GraphQL gives a thread's id and whether it is resolved" — is non-obvious domain knowledge that earns its place, so there is nothing to trim (not 4).

5 / 5

Actionability

There is one copy-paste command (`gh pr view --json number -q .number`) and precise field names, intervals, and output format, but the actual commands and GraphQL queries for steps 2–3 are delegated to "[queries.md](./queries.md) has the commands and GraphQL queries for the steps below" — and that file is absent from the bundle (no references/, scripts/, or assets/ directories; queries.md does not exist), so key executable details are missing. Not 4 because the gap is central rather than minor; not 2 because what is written is specific and directive rather than high-level hints.

3 / 5

Workflow Clarity

A clear numbered 4-step sequence with an explicit polling checkpoint ("Poll `statusCheckRollup` every 30 seconds until no check is pending or in progress") and an explicit completion condition ("Done when all checks are finished and each unresolved thread is in the table"). Not 5 because there is no error-recovery guidance (e.g., a check stuck pending, or Greptile never posting a review); not 3 because checkpoints are explicit, not implicit.

4 / 5

Progressive Disclosure

The split is structurally right — a short overview delegating command/query detail to a clearly signaled, one-level-deep reference — but the referenced ./queries.md does not exist in the bundle, so the primary disclosure path is broken and the deferred content is unavailable. Not 4 because a missing main reference is more than a minor organization gap; not 2 because the body itself is well-structured and the reference is prominently signaled, not buried or inlined.

3 / 5

Total

15

/

20

Passed

Description

83%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 and explicitly states both what the skill does and when to use it, with several concrete actions, natural trigger phrases, and a distinctive Greptile trigger. It is concise with no padding or over-claims. The only weaknesses are minor: the 'what' omits PR-comment and Greptile-summary reporting, and a few natural trigger synonyms (e.g., CI, PR status, ready to merge) are missing.

DimensionReasoningScore

Specificity

"Waits for a PR's checks and reviews to finish, then reports the unresolved review threads, the failing checks and the gaps in the PR description" lists several concrete actions (wait/poll, report threads, report failing checks, report description gaps). It is not 5 because the body's collection step covers five areas and the description's 'what' omits PR comments and the Greptile summary — a minor coverage gap; it is well above 3's '1-2 concrete actions'.

4 / 5

Completeness

Both questions are answered explicitly: the 'what' is the concrete action list, and the 'when' is "Use when the user asks to check a PR, whether a PR is ready, or what the Greptile review found" — concrete trigger phrases matching the anchor-5 pattern. It is not 4 because the 'when' clause is already explicit and specific, leaving nothing weakly implied.

5 / 5

Trigger Term Quality

"check a PR", "whether a PR is ready", and "what the Greptile review found" are natural phrases a user would actually say. It is not 5 because common variations like "CI", "checks", "PR status", or "ready to merge" are missing; it is not 3 because multiple natural, relevant trigger phrases are present rather than just 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The reporting niche (wait for checks/reviews, report what remains) plus the distinctive Greptile trigger carves a clear role. It is not 5 because "check a PR" is somewhat broad and could overlap with closely related PR-review or PR-comment skills; it is not 3 because the Greptile and readiness triggers make it much more than 'somewhat specific'.

4 / 5

Total

17

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 missing, 3 suspicious

Warning

Total

13

/

16

Passed

Repository

storybookjs/storybook

Path

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