CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-pr

Analyze a GitHub pull request including diff, comments, related issues, and local code context

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/review-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a tightly written, highly executable PR review workflow: concrete gh/git/python commands, explicit validation and error-recovery loops, conditional steps, and a clean trigger-gated reference pattern for special cases. The main gaps are the missing referenced bundle file (identifier-normalization.md) and a few spots that could be more precise or trimmed.

Suggestions

Ensure identifier-normalization.md actually ships with the skill bundle — the body links to it but no such file exists alongside SKILL.md, so the triggered read would fail at runtime.

Tighten step 3: the bullet list explaining main/optional/dev dependency categories largely duplicates what the script output already shows; keep only the presentation rules (WARNING blocks, exit-code handling).

Make the CI check matching in step 4 concrete — specify the exact check name pattern or a gh pr checks --json filter instead of the fuzzy 'lint on all python versions / lint*'.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout ('gh pr view PR_ID --json title,body,...', 'git fetch origin devel') and assumes Claude's competence, with only minor trimmable material such as step 3's bullet list explaining dependency categories that partially duplicates the script's own output. Not 5 because a few spots could be tightened.

4 / 5

Actionability

Concrete, executable commands throughout — exact gh invocations with defined JSON fields, the dependency-check script call, and log-fetch commands — with PR_ID substitution clearly defined. Minor gaps keep it below 5: the lint-check match pattern 'lint on all python versions / lint*' is fuzzy, and analysis steps rely on direction rather than commands where commands can't apply.

4 / 5

Workflow Clarity

Clear numbered 1-9 sequence with explicit validation steps and feedback loops: step 1 verifies cwd with pwd, retries with cd, and stops on failure; step 3 branches on script exit codes 1 and 2; step 4 fetches failed-check logs; step 7a requires producing a checklist. Conditional skips are explicit ('If pyproject.toml is not in the diff, skip this step').

5 / 5

Progressive Disclosure

Good structure with a well-signaled, one-level-deep, trigger-gated reference ('read the linked file ONLY when the PR's diff matches the trigger') for identifier-normalization.md. However, that referenced file is not present in the skill bundle (no references/, scripts/, or assets/ directories exist), so the link cannot be verified to resolve — a navigation gap that keeps it below 5.

4 / 5

Total

17

/

20

Passed

Description

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

The description clearly states what the skill does with a concrete enumeration of PR analysis targets, and it sits in a distinct niche. Its main weaknesses are the absence of any 'Use when...' trigger guidance (capping completeness at 3) and missing natural trigger terms like 'review' and 'PR'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to review or analyze a pull request, PR, or the changes in a GitHub PR.'

Include the natural terms users actually say — 'review', 'PR', and 'code review' — alongside 'pull request'.

Optionally mention test coverage or CI checks to make the capability coverage more comprehensive and further distinguish it from generic code-review skills.

DimensionReasoningScore

Specificity

Enumerates several concrete capabilities — 'diff, comments, related issues, and local code context' — matching the 'several specific actions; minor gaps' anchor. Not 5 because it omits coverage the body actually provides (test coverage, CI checks, documentation); not 3 because it lists more than 1-2 actions.

4 / 5

Completeness

Has a clear 'what' ('Analyze a GitHub pull request including diff, comments, related issues, and local code context') but no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'GitHub pull request', 'diff', 'comments', 'related issues'. A few natural terms are missing — most notably 'review' (the skill's core verb) and the common 'PR' abbreviation.

4 / 5

Distinctiveness Conflict Risk

Clear niche (GitHub pull request analysis) with distinct triggers, but minor overlap risk with closely related generic code-review skills that a user could invoke for the same request.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

dlt-hub/dlt

Path

.claude/skills/review-pr/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.