CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

get-pr-comments

Fetch and summarize review comments from the active pull request

Quality

65%

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

Quality

Content

60%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 concise, cleanly sequenced outline for a simple read-only task, but it never descends to an executable level: no gh commands, no API endpoints, no output examples. The dangling LICENSE.txt reference, the unprefixed trailing '---', and the version-number footer are small structural defects that keep an otherwise well-organized simple skill from scoring higher.

Suggestions

Add concrete executable commands for each step, e.g. resolve with 'gh pr view --json number,url' and fetch with 'gh api repos/{owner}/{repo}/pulls/{n}/comments' and '.../pulls/{n}/reviews', so the guidance is copy-paste actionable.

Handle edge cases explicitly: what to do when no active PR exists for the branch, and whether resolved/outdated comment threads are included or filtered.

Fix the trailing structure: remove the stray '---' separator, and either ship the referenced LICENSE.txt in the bundle or drop the reference and version-number footer.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation, but the trailing provenance footer ('From the Cursor Team Kit plugin (cursor/plugins, v1.2.0)... See LICENSE.txt') is trimmable padding that includes a version number — time-sensitive information not placed in a deprecated section. This is a minor instance of content that could be trimmed, matching anchor 4 rather than the every-token-earns-its-place level of 5.

4 / 5

Actionability

All four workflow steps are high-level hints — 'Resolve the active PR', 'Fetch review comments and discussion comments', 'Group feedback by severity and actionability' — with no concrete commands such as 'gh pr view --json url' or 'gh api repos/{owner}/{repo}/pulls/{n}/comments', and no examples of the grouped output format. This matches anchor 2 (high-level hints missing the specific steps to execute); it avoids a 1 because the steps do specify concrete scope and output structure.

2 / 5

Workflow Clarity

The four-step sequence (resolve → fetch → group → return) is clearly ordered and unambiguous, and the read-only task means the destructive/batch validation cap does not apply. Minor gaps remain — no handling for 'no active PR exists' or resolved-vs-unresolved comment threads — keeping it below the explicit-checkpoint level of 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections (Trigger, Workflow, Output), which per the simple-skill exception could merit a 5. However, scoring against the actual bundle, the body references 'LICENSE.txt' which does not exist, and the stray trailing '---' separator makes the provenance footer parse as a second frontmatter block rather than a labeled section — minor organization gaps matching anchor 4.

4 / 5

Total

14

/

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 states a clear, appropriately-scoped capability but omits any 'when to use' trigger guidance and under-specifies what the skill actually does (grouping, prioritized action list). Natural keywords are present but lack the common variations ('PR', 'feedback', 'code review') users would naturally say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to summarize PR feedback, address review comments, or get an overview of pull request reviews.'

Broaden keyword coverage with natural synonyms: 'PR', 'PR feedback', 'code review comments', 'address review comments'.

Mention the fuller set of concrete actions (group by severity/actionability, produce a prioritized action list) so the 'what' is comprehensive, not just 'fetch and summarize'.

DimensionReasoningScore

Specificity

The description names the domain and exactly two concrete actions — 'Fetch and summarize review comments from the active pull request' — matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several specific actions (grouping by severity, producing an action list), so it falls short of a 4, but it is well above the generic-minimal-actions level of a 2.

3 / 5

Completeness

The 'what' is clear (fetch and summarize review comments on the active PR), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It cannot score 4 because 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

'review comments' and 'pull request' are natural phrases, but common variations users actually say — 'PR', 'PR feedback', 'code review', 'address review comments' — are absent. Keyword coverage is relevant but incomplete, matching anchor 3 rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

'Review comments' + 'active pull request' carves a mostly distinct niche with only minor overlap risk against general code-review or PR-inspection skills, matching anchor 4. It lacks the explicit distinct trigger phrasing needed for a 5.

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

novuhq/novu

Path

.agents/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.