CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-pr

Review an existing GitHub pull request and post inline review comments on its diff. Use when the changes are on an opened PR rather than your local working tree.

Quality

78%

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 ./antigravity/skills/review-pr/SKILL.md

The canonical home for this skill is review-pr in NeoLabHQ/context-engineering-kit

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content delivers a genuinely actionable, well-sequenced multi-agent review workflow with concrete commands, scoring thresholds, and posting templates. Its weaknesses are repetition and padding (the same posting guidance repeated three times, plus multiple typos), an unfilled placeholder in the Phase 1 agent prompt, and a monolithic structure that would benefit from splitting templates and examples into reference files.

Suggestions

Move the comment templates, worked examples, and false-positive list into a references/ file (e.g. references/templates.md), keeping SKILL.md as a lean overview of the three phases with clearly signaled one-level-deep links.

Deduplicate the multiple-issue vs single-issue posting guidance (currently stated in Phase 3 step 4, the Notes section, and the template section) into a single posting procedure, and add a concrete JSON payload example for the gh api reviews endpoint.

Fix the unfilled placeholder in the Phase 1 agent prompt ("[pass proper git command that he can use]") with the actual git diff command, and correct typos ("overral", "meangfull", "consitution", "to much noise") that undermine instruction clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient instruction rather than concept explanation, but the multiple-issues vs single-issue gh api guidance is repeated three times, the scoring rubric prose is padded, and typos ("overral", "meangfull", "consitution", "to much noise") add noise — it could clearly be tightened, fitting anchor 3 rather than the noticeably padded level of 2 or the minor-trim level of 4.

3 / 5

Actionability

Provides concrete commands (git diff --stat, gh api endpoints, the MCP inline-comment tool name), argument-resolution pseudocode, and worked comment templates, but has minor gaps: the Phase 1 agent prompt contains an unfilled placeholder ("[pass proper git command that he can use]") and no concrete JSON payload is shown for the review API, so it is not fully copy-paste ready.

4 / 5

Workflow Clarity

The three phases are clearly sequenced with real validation checkpoints (PR eligibility checked in Phase 1 and re-checked in Phase 3, confidence/impact threshold filtering, and an MCP-to-API fallback path), but minor gaps remain: no explicit error-recovery loop if comment posting fails and some steps are loosely worded, keeping it below the explicit feedback-loop level of 5.

4 / 5

Progressive Disclosure

The body is well-sectioned with clear headers, but it is a ~280-line monolith with comment templates, worked examples, and false-positive lists inlined that belong in separate reference files; no bundle files or references exist at all, fitting the some-structure-but-could-be-better-organized anchor.

3 / 5

Total

14

/

20

Passed

Description

82%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 description: it states concrete capabilities and an explicit, disambiguating "Use when" clause that cleanly separates PR review from local-diff review. The only weakness is modest action coverage and missing common synonyms such as "code review".

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("Review an existing GitHub pull request and post inline review comments on its diff") but stops there, matching the 1-2 concrete actions anchor rather than the several-actions coverage of a 4.

3 / 5

Completeness

Explicitly answers both what ("Review an existing GitHub pull request and post inline review comments on its diff") and when ("Use when the changes are on an opened PR rather than your local working tree") with a concrete, precise trigger condition that clearly exceeds the could-be-more-explicit level of a 4.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("pull request", "PR", "diff", "review", "GitHub") that users would actually say, though common variations like "code review" are missing, keeping it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (reviewing opened PRs vs. local working trees) with explicitly stated boundary, giving minimal conflict risk with related review skills.

5 / 5

Total

17

/

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

NeoLabHQ/context-engineering-kit

Path

antigravity/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.