get-pr-comments

Fetch and summarize review comments from the active pull request

Quality

45%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./cursor-team-kit/skills/get-pr-comments/SKILL.md

Quality

Discovery

32%

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 and identifies a clear domain (pull request review comments) with two specific actions, but it lacks a 'Use when...' clause which is critical for skill selection. It also misses common trigger term variations like 'PR', 'code review', and 'feedback' that users would naturally use.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to review PR comments, summarize feedback, or check review status on the current pull request.'

Include common trigger term variations such as 'PR', 'code review', 'reviewer feedback', 'GitHub comments', and 'merge request' to improve matching.

Expand the capability description with additional concrete actions, e.g., 'Fetches, summarizes, and categorizes review comments from the active pull request, highlighting unresolved threads and action items.'

Dimension	Reasoning	Score
Specificity	Names the domain (pull request review comments) and two actions (fetch and summarize), but doesn't list additional concrete actions or details about what summarization entails.	2 / 3
Completeness	Describes what the skill does (fetch and summarize review comments) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and since the 'when' is entirely absent, this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'pull request' and 'review comments', but misses common variations users might say such as 'PR', 'code review', 'feedback', 'PR comments', or 'GitHub reviews'.	2 / 3
Distinctiveness Conflict Risk	Fairly specific to PR review comments which narrows the domain, but could overlap with other PR-related or code review skills since it doesn't clearly delineate its unique niche or scope boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well-structured and concise but critically lacks actionability. It reads more like a high-level task description than an executable skill — there are no concrete commands (e.g., `gh pr view`, `gh api`), no code examples, and no specification of which tools Claude should use to accomplish the steps. The workflow is logically sequenced but too abstract to be directly useful.

Suggestions

Add concrete tool usage instructions — e.g., specific `gh` CLI commands or GitHub API calls to fetch PR comments (`gh pr view --comments`, `gh api repos/{owner}/{repo}/pulls/{number}/comments`).

Provide an example of the expected output format (e.g., a sample grouped feedback summary with severity labels and action items).

Specify how to 'resolve the active PR for the current branch' — e.g., `gh pr view --json number,url` or parsing `git branch --show-current`.

Dimension	Reasoning	Score
Conciseness	The content is lean and avoids explaining concepts Claude already knows. Every line serves a purpose with no padding or unnecessary context.	3 / 3
Actionability	The skill provides only vague, abstract steps ('Fetch review comments', 'Group feedback by severity') with no concrete commands, API calls, code examples, or tool usage instructions. Claude wouldn't know which tools to use or how to execute any of these steps.	1 / 3
Workflow Clarity	Steps are listed in a logical sequence, but there are no validation checkpoints, no error handling, and no specifics on how to resolve the active PR or fetch comments (e.g., which CLI commands or API endpoints to use).	2 / 3
Progressive Disclosure	This is a simple, short skill under 50 lines with no need for external references. The sections are well-organized with clear trigger, workflow, and output sections.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Commit: 7dd9fea

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.