CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-review

Review Nemotron pull requests for critical bugs, tests, and documentation affected by the change.

65

Quality

82%

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 tight, well-scoped review skill: it gives concrete criteria, explicit exclusions, and clear delivery instructions with zero padding. The only minor improvements are organizational (separating criteria from delivery under their own headers) and an example of the expected review comment format.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout ('Focus ONLY on', 'Do NOT comment on', 'post "LGTM"') with no explanation of concepts Claude already knows and no padded sections to trim. Every token earns its place, matching anchor 5.

5 / 5

Actionability

Concrete focus and exclusion lists, explicit delivery channels (inline vs top-level comments), and an explicit no-findings path make the guidance mostly executable. No example of an actual review comment leaves a minor gap, so anchor 4 fits better than 5.

4 / 5

Workflow Clarity

This is a simple single-purpose skill where the single action — apply the focus list to the supplied diff and either comment or post 'LGTM' — is unambiguous, so the simple-skill exception applies. There are no destructive or batch operations that would require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed, and the content is easily navigable. However, a single '## Review context and delivery' header carries the context, criteria, and delivery rules without separating them into distinct sections, leaving minor organization gaps at anchor 4.

4 / 5

Total

18

/

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 is concise, specific, and appropriately scoped to Nemotron pull requests, with good natural trigger terms. Its main weakness is the absence of explicit 'when to use' guidance, which caps completeness at 3.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when reviewing Nemotron pull requests, PRs, or diffs for critical issues.'

Include common synonyms and variations users would naturally say, such as 'PR', 'diff', or 'code review'.

Optionally name the feedback output (inline review comments) to sharpen the 'what' further.

DimensionReasoningScore

Specificity

The description names the domain ('Nemotron pull requests') and several concrete actions ('critical bugs', 'tests', 'documentation affected by the change'). It lists multiple specific review actions but stops short of comprehensive coverage, matching anchor 4 rather than 5.

4 / 5

Completeness

The 'what' is clear (review Nemotron PRs for critical bugs, test coverage, and affected documentation), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like 'pull requests', 'review', 'bugs', 'tests', and 'documentation' are present, but common variations users would say ('PR', 'diff', 'code review') are missing. Good coverage with a few natural terms absent fits anchor 4.

4 / 5

Distinctiveness Conflict Risk

Scoping to 'Nemotron pull requests' makes it mostly distinct, though generic terms like 'review', 'tests', and 'documentation' create minor overlap risk with general code-review skills, matching anchor 4.

4 / 5

Total

15

/

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
NVIDIA-NeMo/Nemotron
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.