CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

get-pr-comments

Fetch and summarize review comments from the active pull request

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./cursor-team-kit/skills/get-pr-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 model of brevity with clean section structure, and the workflow is coherently sequenced for a read-only task with no bundle files to disclose. Its main weakness is actionability: the steps name what to do but never give the concrete commands (e.g., gh CLI invocations or API endpoints) that would make the guidance executable, and edge cases like 'no active PR' are unaddressed. Adding a few specific commands would move this from good to copy-paste-ready.

Suggestions

Add concrete commands to the workflow steps, e.g. 'Resolve the active PR: `gh pr view --json number,url`' and 'Fetch comments: `gh api repos/{owner}/{repo}/pulls/{number}/comments` plus `gh api .../pulls/{number}/comments/review`', so the guidance is executable rather than descriptive.

Specify how to resolve the active PR (e.g., `gh pr status` or branch-name lookup) and what to do when no PR exists for the current branch, closing the workflow's validation gap.

Give one concrete example of the grouping output format (severity buckets with an example action item) so the 'Group feedback by severity and actionability' step is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and efficient: 'Resolve the active PR for the current branch. Fetch review comments and discussion comments. Group feedback by severity and actionability.' — every token earns its place, no concepts Claude already knows are explained, and no padding exists. It matches the 'Lean and efficient; assumes Claude's competence' anchor exactly and is not a 4 because there is nothing to trim.

5 / 5

Actionability

The workflow gives some concrete guidance (distinguishes review comments vs discussion comments, specifies grouping by severity and actionability) but provides no executable commands — no `gh pr view`, `gh api repos/{owner}/{repo}/pulls/{n}/comments`, or equivalent — leaving key details missing, matching the 'Some concrete guidance but incomplete; missing key details' anchor. It is not a 4 because there is no copy-paste-ready command at all, and not a 2 because the steps specify concrete sub-actions rather than being pure high-level hints.

3 / 5

Workflow Clarity

The four-step sequence ('Resolve the active PR', 'Fetch review comments and discussion comments', 'Group feedback', 'Return a concise action list') is clear and logically ordered, matching 'Clear sequence with most checkpoints present; minor validation gaps'. It is not a 5 because there are no explicit checkpoints (e.g., what to do when no active PR exists or when a fetch fails), and not a 3 because the operation is read-only with no destructive risk requiring validation caps, and the sequence itself is unambiguous.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-task, has no bundle files to reference, and is organized into clear Trigger / Workflow / Output sections, so per the simple-skill guidance it matches the top anchor ('well-organized sections' suffice). It is not a 4 because there is no content that belongs in a separate file and no organization gap to point to.

5 / 5

Total

17

/

20

Passed

Description

53%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, in third person, and clearly states what the skill does, but it is missing any 'when to use' trigger guidance and lacks natural synonym variations users would say (e.g., "PR comments", "feedback"). It sits solidly at the midpoint: a clear 'what' with no 'when'. Adding an explicit 'Use when...' clause with natural trigger phrases would lift completeness and trigger-term quality together.

Suggestions

Append a trigger clause such as 'Use when the user asks for a summary of PR feedback, review comments, or code review comments on the active pull request' to satisfy the missing 'when' half of completeness.

Include natural synonym variations users would actually say — 'PR comments', 'code review feedback', 'PR feedback' — to broaden trigger-term coverage.

Optionally mention what the output looks like (e.g., 'grouped by severity and actionability') to sharpen the 'what' and further distinguish it from skills that perform reviews themselves.

DimensionReasoningScore

Specificity

"Fetch and summarize review comments from the active pull request" names the domain (PR review comments) and two concrete actions (fetch, summarize), matching the 'Names domain and 1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because there are only two actions with minor coverage gaps (no mention of grouping, filtering, or output format), and not a 2 because the actions are concrete rather than generic.

3 / 5

Completeness

The description has a clear 'what' (fetch and summarize PR review comments) but no 'Use when...' clause or any trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent rather than weakly implied, and not a 2 because the 'what' is clear and specific.

3 / 5

Trigger Term Quality

Relevant keywords like "review comments" and "pull request" are present, but common variations users would naturally say — "PR comments", "code review feedback", "PR feedback" — are missing, matching the 'Some relevant keywords but missing common variations or synonyms' anchor. It is not a 4 because natural terms like "PR" and "feedback" are absent, and not a 2 because the included keywords are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

"review comments from the active pull request" carves out a fairly distinct niche (summarizing existing PR feedback rather than performing a review), with only minor overlap risk against closely related code-review or PR-management skills, matching the 'Mostly distinct; minor overlap risk' anchor. It is not a 5 because it lacks the explicit trigger phrases that would fully disambiguate it, and not a 3 because the domain is specific rather than broadly overlapping.

4 / 5

Total

13

/

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

cursor/plugins

Path

cursor-team-kit/skills/get-pr-comments/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.