CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ready-for-review

Takes a draft PR that its author approved to a human review. Add the CI label, mark it ready, fix what CI and Greptile find, then request the named reviewer.

Quality

85%

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

100%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.

An exemplary short workflow skill: concrete commands and label names, an explicit repeat-until-green validation loop, a human-in-the-loop checkpoint, and tight authorization scoping, with zero padding. Structure and length are exactly right for a single-purpose slash-command skill.

DimensionReasoningScore

Conciseness

The 28-line body is lean and assumes Claude's competence: every sentence adds non-obvious information such as the authorization scope ('It does not authorize a merge'), Greptile's automatic review, and why post-approval changes must be reported ('the user has not seen those'). Nothing explains concepts Claude already knows.

5 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact commands ('gh pr ready <number>', 'gh pr edit <number> --add-reviewer <login>'), concrete label names (ci:docs, ci:focus, ci:normal, ci:daily), and explicit delegation to named sibling skills for the fix/wait loops. The only open-ended directive ('find the GitHub login') is a reasonable assumption of competence.

5 / 5

Workflow Clarity

The five steps are clearly sequenced with an explicit validation feedback loop ('Repeat until each check on the head commit passed, Greptile reviewed the head commit, and no bot thread is unresolved') plus a human-decision checkpoint ('present it and wait: request no review before the answer'), and the 'After the request' section extends the loop to reviewer comments.

5 / 5

Progressive Disclosure

This is a simple sub-50-line skill with no bundle files and no need for external references; sections are well organized and the sibling-skill links (../build-it, ../check-pr, ../handle-pr-comments) are one level deep and clearly signaled, so the simple-skill exception applies.

5 / 5

Total

20

/

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.

A specific, third-person description with concrete sequenced actions and a distinct niche, weakened only by the absence of an explicit 'Use when...' trigger clause. Adding a one-line usage trigger would lift completeness from 3 toward 5 with no other changes.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the PR author has approved and the PR needs to go to a named human reviewer.'

Mention the final user-notification step so the action list covers the full workflow, e.g., append 'then tell the user the PR is ready.'

DimensionReasoningScore

Specificity

'Add the CI label, mark it ready, fix what CI and Greptile find, then request the named reviewer' lists several specific actions in sequence, matching anchor 4. It falls short of anchor 5's comprehensive coverage because the notify-user step and post-request comment handling from the body are omitted.

4 / 5

Completeness

The 'what' is clear (the four sequenced actions), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the precondition 'that its author approved' only weakly implies the 'when', so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage for the domain: 'draft PR', 'approved', 'human review', 'CI', 'Greptile', 'reviewer'. A few natural terms are missing (e.g., 'pull request' spelled out, 'ready for review'), which fits anchor 4 rather than anchor 3's thinner 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The description pins a very specific workflow niche (post-author-approval to review request, with CI labels, Greptile, and a named reviewer), giving clear distinct triggers and minimal conflict risk with any other skill, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Validation

75%

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

Validation — 12 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 4 suspicious

Warning

Total

12

/

16

Passed

Repository

storybookjs/storybook

Path

.agents/skills/ready-for-review/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.