CtrlK
BlogDocsLog inGet started
Tessl Logo

review-github-pr

Review a GitHub pull request by summarizing its diff and key design decisions. Use when the user wants to review a PR, understand changes in a branch, or get a code review summary. Trigger keywords - review PR, review pull request, summarize PR, summarize diff, code review, review branch, PR summary, diff summary.

71

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

82%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 well-structured, actionable skill body with concrete commands, a clear step sequence, and good fallback handling. The main improvement area is making validation checkpoints more explicit in the workflow.

Suggestions

Mark validation/decision gates explicitly (e.g., '**Verify**: confirm exactly one PR was found before proceeding') to raise workflow clarity.

Tighten the Potential Concerns guidance block, which is the densest section and could be trimmed without losing the behavioral-comparison instruction.

Consider extracting the full summary-format template into a references file so the body stays a lean overview.

DimensionReasoningScore

Conciseness

Mostly lean and instruction-focused with executable commands rather than concept explanations, though the Potential Concerns and large-diff sections carry guidance that could be tightened slightly.

4 / 5

Actionability

Provides copy-paste-ready commands ('gh pr view <number> --json ...', 'gh pr diff <number>', 'git diff origin/<target>...origin/<source>') plus a concrete summary template covering the common PR-number and branch-name cases.

5 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced with explicit branch handling (multiple/no PR, gh diff failure fallback); read-only so no destructive-cap applies, but validation checkpoints are implicit rather than bolded 'Validate' steps.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear sections (Prerequisites, Steps, Commands Reference, Examples) and no nested references; no bundle files exist to split out, so structure is appropriate with only minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

95%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, well-structured description that clearly states the skill's purpose and trigger conditions with a comprehensive keyword list. Third-person voice is used correctly throughout.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'summarizing its diff and key design decisions', 'understand changes in a branch', 'get a code review summary' — though several are restatements of the same core actions rather than distinct capabilities, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' ('Review a GitHub pull request by summarizing its diff and key design decisions') and 'when' ('Use when the user wants to review a PR, understand changes in a branch, or get a code review summary') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive list of natural trigger terms with synonyms — 'review PR, review pull request, summarize PR, summarize diff, code review, review branch, PR summary, diff summary' — covering the phrases a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche — GitHub PR review — with distinct triggers unlikely to fire for unrelated skills; minimal conflict risk.

5 / 5

Total

19

/

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.

Validation13 / 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

Warning

Total

13

/

16

Passed

Repository
NVIDIA/OpenShell
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.