CtrlK
BlogDocsLog inGet started
Tessl Logo

address-github-comments

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

78

1.20x
Quality

71%

Does it follow best practices?

Impact

88%

1.20x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/address-github-comments/SKILL.md

The canonical home for this skill is address-github-comments in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

A concise, well-structured skill with executable gh commands and a clear workflow. Its main weakness is the absence of a verification step before claiming comments are addressed, which caps workflow clarity.

Suggestions

Insert a verification checkpoint between 'Apply Fixes' and 'Respond to Comments' (e.g., run tests/lint or re-read the diff) and only post the resolution once it passes.

Replace the vague 'Apply the code changes for the selected comments' with concrete guidance on how to locate and apply each fix.

Remove or sharpen the filler 'When to Use' line so it does not merely restate the overview.

DimensionReasoningScore

Conciseness

The body is lean with executable commands and tight sections; the only padding is the redundant 'When to Use' line that restates the overview, which is a minor trim candidate.

4 / 5

Actionability

Provides concrete, executable commands (gh auth status, gh pr view --comments, gh pr comment) for most steps, though 'Apply the code changes' and 'use a custom script if available' lack specific execution detail.

4 / 5

Workflow Clarity

A clear 4-step sequence with a user-confirmation checkpoint exists, but there is no validation that fixes actually work before posting 'Addressed in latest commit'; for batch/PR-output operations this missing verification caps the score at 3.

3 / 5

Progressive Disclosure

The skill is under ~50 lines, single-purpose, requires no external references, and is organized into clearly labeled sections (Overview, Prerequisites, Workflow, Common Mistakes), meeting the simple-skill exception for a top score.

5 / 5

Total

16

/

20

Passed

Description

70%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.

A solid, third-person description with an explicit 'Use when' trigger and a distinct niche. It is held back from the top band by limited action specificity and a 'when' clause that echoes the 'what' rather than introducing varied trigger phrases.

Suggestions

Add 1-2 more concrete actions (e.g., 'reply to threads, resolve conversations, and track outstanding comments') to lift specificity.

Expand the trigger clause with natural synonyms users actually say, such as 'PR feedback', 'resolve review comments', or 'respond to PR threads'.

DimensionReasoningScore

Specificity

Names the domain ('review or issue comments on an open GitHub Pull Request') and the tool ('gh CLI') with one concrete action ('address'), but does not enumerate multiple specific actions, so it is not comprehensive.

3 / 5

Completeness

The 'Use when...' clause answers both what (address PR comments via gh) and when (when addressing review/issue comments), but the 'when' largely restates the 'what' rather than giving distinct, concrete trigger scenarios.

4 / 5

Trigger Term Quality

Includes natural terms like 'review or issue comments' and 'Pull Request' that users would say, but omits common synonyms such as 'PR', 'feedback', and 'resolve/respond to comments'.

4 / 5

Distinctiveness Conflict Risk

It targets a clear niche (handling PR comments via gh CLI) with minimal conflict risk, though it could overlap slightly with broader PR-review or git workflow skills.

4 / 5

Total

15

/

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.