CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-review-response

Teaches agents to reply to PR review comment threads after fixing issues, making resolutions traceable

60

Quality

71%

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 ./.squad/skills/pr-review-response/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable with executable commands, a clear sequenced workflow, and strong guardrails via anti-patterns. It is well-organized for a single-file skill; the main lever is trimming redundant example blocks or offloading some examples to a reference file.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no padding about what PRs or libraries are — though several near-duplicate example reply blocks and repeated push-back examples add tokens that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready `gh api` REST and GraphQL commands with specific examples covering apply-suggestion, push-back, and multi-comment cases.

5 / 5

Workflow Clarity

A clear 5-step sequence is given with explicit guardrails (reply only after pushing, reply to top-level comments only, resolve rules, a STOP step) and anti-patterns that act as validation checkpoints for the batch reply operation.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is a single well-organized SKILL.md with clear section headers and one-level navigation, though the example library is sizable enough that splitting some into a reference file would tighten the overview.

4 / 5

Total

18

/

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 clearly states a specific purpose and is reasonably distinct, but it lacks an explicit trigger/use-when clause and broader keyword coverage, which limits completeness and trigger-term quality. Adding a natural "Use when ..." sentence with synonyms would raise the top dimensions.

Suggestions

Append an explicit trigger clause, e.g. ". Use when responding to PR review feedback, addressing Copilot suggestions, or resolving reviewer-requested changes."

Add natural synonyms users actually say ("review comments", "review feedback", "resolve threads") to improve trigger-term coverage.

Broaden the action list slightly (e.g. "reply to threads, resolve them, and reference fixes in commit messages") for more comprehensive specificity.

DimensionReasoningScore

Specificity

Names the domain ("PR review comment threads") and two concrete actions ("reply to ... threads", "making resolutions traceable"), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

The description has a clear "what" but no explicit "when/Use when" guidance; per the judging guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "PR review comment threads" and "resolutions" appear, but there are no synonyms or natural user variations and no explicit "Use when..." trigger phrase in the description.

3 / 5

Distinctiveness Conflict Risk

The niche (replying to PR review comment threads for traceability) is fairly distinct from other skills with only minor overlap risk against general PR/commit skills, fitting the "mostly distinct" anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
bradygaster/squad
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.