address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
80
73%
Does it follow best practices?
Impact
88%
1.20xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/address-github-comments/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with clear trigger guidance and good distinctiveness. Its main weakness is that the specific actions are somewhat vague—'address review or issue comments' could be more concrete by listing specific operations like replying, resolving, or dismissing. The 'Use when' clause and natural trigger terms are well done.
Suggestions
List more specific concrete actions such as 'reply to review comments, resolve comment threads, dismiss stale reviews' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (GitHub Pull Request comments) and a general action (address review or issue comments), but doesn't list specific concrete actions like 'reply to comments', 'resolve threads', 'request changes', or 'dismiss reviews'. | 2 / 3 |
Completeness | Explicitly answers both what ('address review or issue comments on an open GitHub Pull Request using the gh CLI') and when ('Use when you need to address review or issue comments'), with a clear 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'review comments', 'issue comments', 'GitHub Pull Request', 'PR', 'gh CLI'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to a specific niche: addressing comments on open GitHub PRs via gh CLI. This is distinct from general GitHub skills, code review skills, or PR creation skills, making conflicts unlikely. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable skeleton for addressing PR comments but falls short on actionability—particularly Step 3 which is entirely abstract. The workflow lacks validation steps (e.g., running tests after fixes) and the 'When to Use' section adds no value. The concrete `gh` commands provided are helpful but insufficient to make this a fully actionable guide.
Suggestions
Make Step 3 (Apply Fixes) concrete with specific guidance or examples, such as how to locate the file/line from a review comment and apply changes.
Add a validation step after applying fixes (e.g., run tests, lint) before responding to comments as resolved.
Remove the tautological 'When to Use' section and the obvious advice in 'Common Mistakes' to improve conciseness.
Consider adding an example of using `gh api` to fetch review comments with file/line context for more precise fix targeting.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary filler like the 'When to Use' section which is tautological, and the 'Common Mistakes' section states obvious things Claude already knows (like reading surrounding code context). | 2 / 3 |
Actionability | Provides some concrete commands (`gh pr view --comments`, `gh pr comment`), but Step 3 ('Apply the code changes for the selected comments') is entirely vague with no concrete guidance. The 'Or use a custom script if available' is also hand-wavy. | 2 / 3 |
Workflow Clarity | Steps are listed in a reasonable sequence and there's a user confirmation checkpoint in step 2, but step 3 lacks any specifics, there's no validation after applying fixes (e.g., running tests), and no feedback loop for verifying the changes actually address the comments. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope (under 50 lines, single workflow), the content is well-organized into clear sections with logical progression from prerequisites through workflow to common mistakes. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
d739c8b
- 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.