address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
Install with Tessl CLI
npx tessl i github:Dokhacgiakhoa/antigravity-ide --skill address-github-commentsOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
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 minimal - it's essentially a table of contents pointing to sub-skills without providing any substantive guidance in the main file. While concise, it sacrifices actionability and workflow clarity by delegating everything to sub-files without explaining the overall process or providing any executable examples.
Suggestions
Add a brief workflow summary (3-5 sentences) explaining the overall process before linking to sub-skills, so users understand the sequence without needing to open each file
Include at least one concrete example command for a common operation (e.g., fetching PR comments with `gh pr view --comments`)
Add validation checkpoints to the workflow overview, such as 'verify all comments addressed before marking resolved'
Fix the malformed 'Workflow' section - the header appears but has no content before the knowledge modules list
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations. Every section serves a purpose and assumes Claude's competence with basic concepts. | 3 / 3 |
Actionability | Provides a concrete auth check command, but the main workflow delegates entirely to sub-skills without any executable guidance in the main file. The skill itself contains no actionable steps for addressing comments. | 2 / 3 |
Workflow Clarity | The workflow section is essentially empty - it just lists links to sub-skills without describing the actual sequence, validation checkpoints, or 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 file 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
91%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 | |
- 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.