CtrlK
BlogDocsLog inGet started
Tessl Logo

address-pr-comments

Address review comments (including Copilot comments) on the active pull request. Use when: responding to PR feedback, fixing review comments, resolving PR threads, implementing requested changes from reviewers, addressing code review, fixing PR issues.

75

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 tight, well-sequenced procedure that names exact tools and fields, includes validation/refresh checkpoints, and stays free of padding or unnecessary explanation. It is an exemplary concise, actionable skill body.

DimensionReasoningScore

Conciseness

Lean procedural body with no concept-explanation padding; every line is actionable and assumes Claude's competence, e.g. 'Call the github-pull-request_currentActivePullRequest tool.'

5 / 5

Actionability

Provides concrete tool identifiers and specific result fields throughout ('github-pull-request_resolveReviewThread', 'lastUpdatedAt', 'isResolved', 'canResolve', 'commentType'), giving fully actionable guidance for an instruction-only skill.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit checkpoints: the step-1 refresh logic based on lastUpdatedAt, the step-5 Verify step, and the canResolve gating in step-6 form a feedback loop appropriate to batch thread resolution.

5 / 5

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no bundle files and well-organized section headers, qualifying for the top anchor under the simple-skills exception.

5 / 5

Total

20

/

20

Passed

Description

87%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 specific, trigger-rich, and explicitly pairs a clear 'what' with a concrete 'Use when' clause, fitting a high-quality skill description. Minor additional synonym coverage would push specificity and trigger_term_quality to the top anchor.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Address review comments', 'fixing review comments', 'resolving PR threads', 'implementing requested changes') with minor gaps; not a maximal 5 because the actions are phrased at the review-response level rather than enumerating distinct concrete operations.

4 / 5

Completeness

Clearly answers what ('Address review comments ... on the active pull request') and explicitly answers when with a 'Use when:' clause followed by concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say ('responding to PR feedback', 'fixing review comments', 'addressing code review', 'fixing PR issues') with several synonyms; a few common variations are absent, keeping it just below 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (active pull request review comments, including Copilot comments) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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
microsoft/vscode-pull-request-github
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.