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.

67

Quality

81%

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

72%Weight 40%Scale 1-3

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 procedural skill with executable commands and a clear sequence, weakened mainly by redundant reference/example sections and implicit rather than explicit validation checkpoints.

Suggestions

Remove the 'Useful Commands Reference' table or the 'Example Usage' section, since both restate commands and steps already shown in Steps 1-5, to improve token efficiency.

Add explicit validation checkpoints (e.g., verify the diff was fetched and is non-empty before summarizing; confirm 'git fetch' succeeded before diffing) to raise workflow clarity.

Add a brief feedback loop for the fallback path (what to do if 'git fetch' or the local diff fails) so error recovery is explicit rather than implied.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining known concepts, but the 'Useful Commands Reference' table and 'Example Usage' section restate commands and steps already shown inline, adding redundant tokens.

2 / 3

Actionability

It provides concrete, copy-paste-ready commands throughout ('gh pr list --head "<branch>" --state open', 'gh pr view <number> --json ...', 'gh pr diff <number>', 'git diff origin/<target>...origin/<source>') and a fully specified summary template.

3 / 3

Workflow Clarity

The five-step sequence with explicit decision branches (PR number vs branch, primary vs fallback diff) is clear, but validation checkpoints are implicit rather than explicit validate-then-proceed gates, and there is no feedback loop for fetch/diff failures.

2 / 3

Progressive Disclosure

The skill is a self-contained, well-organized document with clean section headers and no nested or external references; for a procedural skill needing no bundle files, well-organized sections satisfy progressive disclosure.

3 / 3

Total

10

/

12

Passed

Description

90%Weight 40%Scale 1-3

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-scoped description with explicit what/when guidance and excellent natural trigger keywords; its only weakness is a somewhat narrow set of concrete actions. It uses third-person voice correctly.

DimensionReasoningScore

Specificity

It names the domain (GitHub PR) and concrete actions ('summarizing its diff and key design decisions'), but offers only two closely-related actions rather than a broad, varied list of specific capabilities.

2 / 3

Completeness

It 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...') with an explicit trigger clause.

3 / 3

Trigger Term Quality

It provides strong coverage of natural terms users would say ('review PR', 'review pull request', 'summarize PR', 'summarize diff', 'code review', 'review branch', 'PR summary', 'diff summary').

3 / 3

Distinctiveness Conflict Risk

The PR-review niche is clearly scoped with distinct triggers unlikely to conflict with unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

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.