CtrlK
BlogDocsLog inGet started
Tessl Logo

address-pr-comments

Read PR review comments, evaluate validity, implement fixes, push changes, and reply/resolve threads

64

Quality

76%

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

Quality

Content

81%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 and exceptionally well-structured with strong validation feedback loops, making it a strong workflow skill. The main weakness is repetition of the author-filter rule across multiple subsections and a slightly long monolithic form that could benefit from selective reference splitting.

Suggestions

State the author-filter rule once in step 2d and reference it from 2b/2c instead of repeating the full allow-list three times, reducing token cost.

Consider moving the long GraphQL pagination queries into a `scripts/` or `references/` file referenced from the body to shorten the main SKILL.md overview.

Tighten the security block by leading with the one-sentence rule and demoting the extended rationale to a short note.

DimensionReasoningScore

Conciseness

The body is mostly efficient and command-dense, but the author-filter rule ("only read comments from $MY_LOGIN, chatgpt-codex-connector...") is restated in 2b, 2c, and 2d, and the security block is lengthy, so it could be tightened.

3 / 5

Actionability

Provides fully executable, copy-paste-ready `gh`, `git`, and `docker run` commands with decision matrices and concrete test commands, covering the common cases with clearly documented placeholders.

5 / 5

Workflow Clarity

An 8-step sequence with explicit validation in step 5 (run tests) and a feedback loop ("If tests fail, iterate on the implementation fix"), plus a final summary checklist, satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with coherent linear flow, but it is a single ~250-line monolithic file with no reference bundle; long GraphQL queries and the security block could optionally be split out.

4 / 5

Total

17

/

20

Passed

Description

71%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 strong on specificity and distinctiveness, listing concrete actions in a clear third-person voice, but it lacks an explicit "Use when..." trigger clause and could broaden its natural keyword coverage. Adding trigger guidance and synonyms would raise the capped completeness score.

Suggestions

Append an explicit "Use when..." clause (e.g., "Use when addressing code review feedback on a pull request") so the "when" is stated, not just the "what".

Broaden trigger terms to include natural synonyms like "code review", "pull request", and "review feedback" so users' phrasings match more reliably.

Spell out "pull request" at least once alongside "PR" to widen the match surface for natural language.

DimensionReasoningScore

Specificity

Lists five concrete actions ("Read PR review comments, evaluate validity, implement fixes, push changes, and reply/resolve threads"), giving comprehensive coverage of the skill's capabilities rather than vague language.

5 / 5

Completeness

The description clearly answers "what" with concrete actions but contains no "Use when..." clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes the natural phrase "PR review comments" but omits common synonyms a user might say such as "code review", "pull request", or "feedback", so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The PR-review-comment-addressing niche is clearly distinguishable from other skills, with only minor overlap risk against closely related git/PR skills.

4 / 5

Total

16

/

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
DataDog/rshell
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.