CtrlK
BlogDocsLog inGet started
Tessl Logo

review-pr

Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

78

Quality

98%

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

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

A lean, highly actionable review workflow with strong validation gates and confirmation checkpoints; the only gap is the absence of any progressive-disclosure bundle files for a skill of this length.

Suggestions

Consider extracting the draft template and gh command payload examples into a references/ file so SKILL.md stays a concise overview that loads detail on demand.

The editorial-fit question list (section 3) could be split into a short rubric reference, keeping the main body focused on the decision flow.

DimensionReasoningScore

Conciseness

Dense imperative prose with no padding or explanations of concepts Claude already knows; every section (gather context, research, editorial fit, verdict, placement, drafts, posting) earns its tokens.

5 / 5

Actionability

Provides fully executable gh commands (gh pr view --json, gh api pulls/comments, gh pr diff, POST reviews, gh pr comment --body-file), an exact JSON payload shape, and a copy-paste draft template.

5 / 5

Workflow Clarity

Clear numbered sequence with explicit validation checkpoints — two-phase confirmation gate, re-fetch head SHA before posting, stop if changed, verify posted results and report URLs — exactly the feedback-loop pattern for mutating operations.

5 / 5

Progressive Disclosure

Well-organized into clear numbered sections and a Definition of done with no nested references, but the skill is a single ~190-line self-contained file with no bundle files to delegate detail to.

4 / 5

Total

19

/

20

Passed

Description

100%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 strong, specific description that states concrete capabilities, provides natural trigger phrases, answers both what and when, and explicitly disambiguates from a sibling skill.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'validate technical claims', 'assess editorial fit and information architecture', 'choose a verdict', 'draft exact inline or PR-wide feedback behind a confirmation gate' — covering the review workflow comprehensively.

5 / 5

Completeness

Explicitly answers both what (validate claims, assess fit, choose verdict, draft feedback) and when ('Use for requests such as...'), plus a negative boundary ('Do not use to maintain or fix a PR you own').

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", "help review backlog PRs" — with synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Niche is clearly scoped to Docker documentation PR review, with explicit disambiguation against maintain-pr, minimizing conflict risk.

5 / 5

Total

20

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
docker/docs
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.