address-github-comments

Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.

Quality

51%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/address-github-comments/SKILL.md

Quality

Discovery

50%

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 has a proper 'Use when' structure which is good, but it's light on specifics about what actions can be performed. It names the domain clearly (GitHub PR comments via gh CLI) but lacks concrete action verbs and comprehensive trigger terms that users would naturally use.

Suggestions

Add specific concrete actions like 'reply to review comments, resolve comment threads, mark conversations as resolved, respond to requested changes'

Include more natural trigger terms users might say: 'PR feedback', 'code review comments', 'reviewer feedback', 'respond to reviewer'

Expand the 'what' portion before the 'Use when' clause to clearly state capabilities, e.g., 'Responds to and resolves review comments and issue comments on GitHub Pull Requests using gh CLI.'

Dimension	Reasoning	Score
Specificity	Names the domain (GitHub PR comments) and implies actions (address review/issue comments), but doesn't list specific concrete actions like 'reply to comments', 'resolve threads', 'request changes'.	2 / 3
Completeness	Has a 'Use when' clause which addresses the 'when', but the 'what' is weak - it says 'address' comments but doesn't explain what specific actions or capabilities are available.	2 / 3
Trigger Term Quality	Includes relevant terms like 'review comments', 'issue comments', 'Pull Request', 'GitHub', 'gh CLI', but missing common variations users might say like 'PR feedback', 'code review', 'respond to reviewer'.	2 / 3
Distinctiveness Conflict Risk	Reasonably specific to PR comments via gh CLI, but could overlap with general GitHub skills or PR management skills. The focus on 'comments' specifically helps distinguish it somewhat.	2 / 3
	Total	8 / 12 Passed

Implementation

52%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is extremely concise but sacrifices too much actionability and workflow clarity. The main file serves only as a table of contents with no substantive guidance, making it unclear how the sub-skills connect or what the overall process looks like. The empty workflow section and lack of any inline examples or validation steps significantly reduce its utility.

Suggestions

Add a brief numbered workflow summary showing how the 4 sub-skills connect sequentially (e.g., '1. Inspect → 2. Categorize → 3. Fix → 4. Respond')

Include at least one concrete example command for fetching PR comments (e.g., `gh pr view <number> --comments`)

Add a validation checkpoint indicating when to verify all comments have been addressed before marking complete

Provide a brief description of what each sub-skill covers inline, not just links

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, with no unnecessary explanations. It assumes Claude knows what GitHub CLI is and how authentication works, providing only the essential commands and structure.	3 / 3
Actionability	Provides concrete auth check command, but the actual workflow is entirely delegated to sub-skills with no inline examples or executable guidance for the core task of addressing comments.	2 / 3
Workflow Clarity	The workflow section is essentially empty - it only lists links to sub-skills without any sequence, validation checkpoints, or explanation of how the steps connect. No feedback loops or error handling are mentioned.	1 / 3
Progressive Disclosure	References sub-skills appropriately (one level deep), but the main skill provides almost no overview content - it's too sparse to serve as a useful entry point. The 'Workflow' section header has no content before the links.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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: Dokhacgiakhoa/antigravity-ide
Commit: 332e58b

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.