CtrlK
BlogDocsLog inGet started
Tessl Logo

handle-pr-comments

Triage and resolve GitHub PR review comments one by one, interactively. Use when the user asks to handle, address, respond to, or resolve PR review comments, or mentions reviewer feedback on a pull request.

76

Quality

94%

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

93%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 is concise, highly actionable, and well-structured for a simple single-purpose workflow, with concrete GraphQL/gh details and a clear per-comment loop. The only minor gap is the absence of an explicit verification step (e.g., run tests/build) after applying a fix before committing in this batch operation.

Suggestions

Add an explicit verification checkpoint after applying a fix (e.g., run tests/lint/build) before committing, since this is a batch operation applying code changes — the human confirmation gate partially covers this but an automated verify step would close the gap.

Consider noting how to detect/handle already-outdated or no-longer-relevant threads (isOutdated is requested but its handling is not specified in the loop).

Clarify what 'reply only' produces (e.g., a GraphQL addComment / addPullRequestReviewComment mutation) so the reply action is as concrete as the resolve action.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, giving direct instructions with no padding or explanation of concepts Claude already knows (PRs, GraphQL).

5 / 5

Actionability

Provides fully executable guidance: concrete `gh pr view`, named GraphQL fields and the `resolveReviewThread` mutation, and explicit AskQuestion options (apply suggested fix / apply a different fix / reply only / skip).

5 / 5

Workflow Clarity

A clearly numbered 4-step sequence with per-comment sub-steps and human-in-the-loop checkpoints (AskQuestion, ask whether to commit), though it lacks an explicit automated verify-after-change feedback loop for the batch operation.

4 / 5

Progressive Disclosure

A short, single-purpose skill (under 50 lines) with well-organized sections and numbered steps; no external references are needed, so the simple-skill exception applies.

5 / 5

Total

19

/

20

Passed

Description

95%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 well-crafted: it states concrete capabilities in third person and pairs them with an explicit, synonym-rich 'Use when...' trigger clause. It cleanly answers both what the skill does and when to invoke it with minimal conflict risk.

DimensionReasoningScore

Specificity

Names the domain (GitHub PR review comments) and several concrete actions (triage, resolve, one by one, interactively), with minor gaps in action coverage rather than the comprehensive list of a 5.

4 / 5

Completeness

Clearly answers both 'what' (triage and resolve PR review comments one by one, interactively) and 'when' via an explicit 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms ('handle, address, respond to, or resolve') plus 'reviewer feedback on a pull request', matching the comprehensive-with-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (GitHub PR review comment triage/resolution) with distinct triggers, making conflict with unrelated skills minimal.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
storybookjs/storybook
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.