CtrlK
BlogDocsLog inGet started
Tessl Logo

get-pr-comments

Fetch and summarize review comments from the active pull request

58

Quality

66%

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

71%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 exceptionally concise and well-structured for a simple read-only skill, but its workflow steps lack concrete executable commands, weakening actionability.

Suggestions

Add specific commands to the workflow steps, e.g. resolving the PR with `gh pr view --json number` and fetching comments with `gh pr view --comments` or the GraphQL API.

Give a concrete example of the grouped output format so the "Return a concise action list" step is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation or padding; every line (Trigger, four-step Workflow, Output) earns its place and assumes Claude's competence.

5 / 5

Actionability

Steps like "Resolve the active PR" and "Fetch review comments and discussion comments" are high-level hints with no concrete commands (e.g. `gh pr view --comments`), so the specific execution path is missing.

2 / 5

Workflow Clarity

The four steps form a clear, ordered sequence; the operation is read-only so the destructive/batch validation cap does not apply, though no explicit checkpoints are given.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized Trigger/Workflow/Output sections and no need for external references, fitting the simple-skill exception for a top score.

5 / 5

Total

16

/

20

Passed

Description

61%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 states a clear, third-person purpose with natural trigger terms but omits an explicit "Use when..." usage clause, leaving the "when" weakly implied and capping completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants a summary of feedback on the current pull request or asks about review comments."

Add common synonyms ("PR feedback", "code review comments") to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Fetch and summarize review comments" names the PR-review domain with two concrete actions, matching the anchor for domain-plus-1-2-actions without being comprehensive.

3 / 5

Completeness

A clear "what" is present (fetch and summarize review comments), but there is no "Use when..." trigger clause, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

"pull request" and "review comments" are natural phrases users would say, giving good keyword coverage, though synonyms like "PR feedback" or "code review" are absent.

4 / 5

Distinctiveness Conflict Risk

Scoping to review comments on the active pull request carves a distinct niche with only minor overlap risk against general code-review or git skills.

4 / 5

Total

14

/

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
cursor/plugins
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.