CtrlK
BlogDocsLog inGet started
Tessl Logo

review-a-contributor-pr

Review a fork PR, review an external contributor PR, check DCO sign-off, check ee/ CLA, carry a fork commit into a same-repo branch, is this PR safe to merge. Checklist for pull requests from forks before a human approves or merges them.

72

Quality

88%

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

88%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 dense, executable reviewer checklist with strong command coverage, explicit validation gating, and clear sequencing. The dated rationale paragraph and absence of bundle-file references are the only minor gaps.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no basic-concept explanations, just commands plus tight bullets — but the dated intro rationale paragraph (PR #4733/#4709, 'merged on 2026-09-09') and a few prose rationale lines could be tightened, so anchor 4 rather than 5.

4 / 5

Actionability

Copy-paste-ready, executable bash commands with real gh/git invocations and --jq filters cover the common cases (DCO, CLA label, warden checks, diff reading, surface grep, cherry-pick carry), matching anchor 5.

5 / 5

Workflow Clarity

Seven numbered sections with explicit validation gating ('Blocked on any item means no approval and no merge'), feedback loops (re-run sections 1, 3, 4, 5 when the head changes), and a final OK/Blocked/N/A review-recording checklist; the destructive-skill cap does not apply because validation is present, matching anchor 5.

5 / 5

Progressive Disclosure

Self-contained SKILL.md with seven clear section headers, no nested references, and no mis-placed bulk content — well organized, but it carries no one-level-deep bundle references (none exist), so it sits at anchor 4 rather than the reference-bearing anchor 5.

4 / 5

Total

18

/

20

Passed

Description

87%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 answers both what the skill does and when to use it, with concrete fork/DCO/CLA triggers in third-person voice. Minor redundancy in phrasing keeps specificity just below the top anchor.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'check DCO sign-off', 'check ee/ CLA', 'carry a fork commit into a same-repo branch', 'is this PR safe to merge' — but is somewhat repetitive ('Review a fork PR, review an external contributor PR') and not fully comprehensive over all reviewer tasks, so it sits at anchor 4 rather than 5.

4 / 5

Completeness

It answers both 'what' (review fork PRs for DCO, CLA, carry commits, merge safety) and 'when' via the explicit clause 'Checklist for pull requests from forks before a human approves or merges them', which is an explicit trigger context matching anchor 5.

5 / 5

Trigger Term Quality

Natural maintainer-facing keywords are well covered ('fork PR', 'external contributor PR', 'DCO sign-off', 'CLA', 'safe to merge', 'pull requests from forks'), but a few natural variants a user might say ('PR from a fork', 'signed-off-by', 'DCO check') are missing, matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

The fork-PR + DCO + CLA + carry-commit combination is a clear niche with distinct triggers and minimal overlap with generic PR-review or code-review skills, matching anchor 5.

5 / 5

Total

18

/

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
different-ai/openwork
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.