CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-address-comments

Use this skill if the user asks you to help them address GitHub PR comments for their current branch of the Gemini CLI. Requires `gh` CLI tool.

63

Quality

74%

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 ./.gemini/skills/pr-address-comments/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-structured review procedure with a concrete runnable script and explicit human-in-the-loop checkpoints, appropriately offloading logic to a bundled script. Minor gaps are the lack of an example summary format and any error-recovery guidance.

DimensionReasoningScore

Conciseness

The ~12-line body is lean and assumes Claude can analyze diffs and commit logs, with only minor redundancy between the opening sentence and the 'OBJECTIVE' line that could be trimmed.

4 / 5

Actionability

It gives a concrete runnable command ('Run the `scripts/fetch-pr-info.js` script') and specific output-formatting rules (✅ for resolved, [1] reference numbers for open), but lacks an example of the summary format, leaving a minor gap.

4 / 5

Workflow Clarity

The three-step procedure is clearly sequenced with explicit checkpoints ('MAKE SURE you read the entire output' and 'allow the user to guide you... DO NOT begin fixing issues automatically'), but there is no error-recovery feedback loop, fitting 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

The short body is well-organized under one section header and references a single real one-level bundle file (`scripts/fetch-pr-info.js`) with logic appropriately split out, matching 'clear overview with well-signaled one-level-deep references'.

5 / 5

Total

17

/

20

Passed

Description

70%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 clear and includes an explicit 'Use this skill if...' trigger with a concrete tool dependency, but it describes only a single generic action and provides limited trigger-term variations. It is solid but not comprehensive.

Suggestions

Enumerate the concrete actions the skill performs (e.g., 'fetch PR comments, summarize resolved vs. open threads, and draft replies') to raise specificity beyond the single generic verb 'address'.

Add natural trigger synonyms users might say, such as 'pull request', 'code review', or 'resolve PR comments', to broaden trigger-term coverage.

Clarify the 'when' with multiple trigger phrasings (e.g., 'Use when the user asks to review, reply to, or resolve comments on an open PR').

DimensionReasoningScore

Specificity

The description names the domain ('address GitHub PR comments for their current branch of the Gemini CLI') and one concrete action, but 'address' is generic and no further actions are enumerated, matching the anchor for one-to-two concrete actions without comprehensive coverage.

3 / 5

Completeness

It explicitly answers both what ('address GitHub PR comments') and when ('Use this skill if the user asks you to help them address GitHub PR comments for their current branch'), but the 'when' offers a single trigger phrasing rather than multiple concrete trigger variations, fitting the anchor where 'when' could be more explicit.

4 / 5

Trigger Term Quality

It includes natural phrases a user would say ('PR comments', 'GitHub PR', 'help them address'), but misses common variations like 'pull request' (full form), 'code review', or 'resolve comments', leaving a few natural terms absent.

4 / 5

Distinctiveness Conflict Risk

The niche is fairly specific (addressing PR comments for the current branch of the Gemini CLI, requiring `gh`), but it could overlap with general PR-review or GitHub skills, matching 'mostly distinct; minor overlap risk with closely related skills'.

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
google-gemini/gemini-cli
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.