gh-pr-inline
Post inline comments on GitHub PRs and respond to review feedback via gh api
83
75%
Does it follow best practices?
Impact
96%
1.29xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./dot_config/opencode/skill/gh-pr-inline/SKILL.mdQuality
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 is specific about what it does (posting inline comments, responding to review feedback via gh api) and occupies a clear niche, but it critically lacks any 'Use when...' guidance and misses common trigger term variations like 'pull request', 'code review', or 'PR comment'. Adding explicit trigger conditions and broader keyword coverage would significantly improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to comment on a pull request, reply to code review feedback, or post inline PR comments.'
Include common trigger term variations like 'pull request', 'code review', 'PR comment', 'reply to reviewer', and 'review discussion'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Post inline comments on GitHub PRs' and 'respond to review feedback'. Also specifies the tool used ('gh api'), which adds technical specificity. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes good natural keywords like 'inline comments', 'GitHub PRs', 'review feedback', and 'gh api', but misses common variations users might say such as 'pull request', 'code review', 'PR comment', 'reply to review', or 'review comment'. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a clear niche: inline PR comments and review feedback via gh api. This is distinct from general GitHub skills, git commit skills, or broader code review tools, making conflicts unlikely. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that efficiently addresses a non-obvious gap in the `gh` CLI (inline PR comments requiring `gh api`). It provides complete, executable examples for all key operations, includes a clear decision workflow for responding to feedback, and handles edge cases like multi-line comments and misplaced comment deletion. The content is lean, well-structured, and immediately actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. The opening immediately explains why the non-obvious approach is needed, and the rest is lean, practical guidance with no unnecessary explanation of concepts Claude already knows. | 3 / 3 |
Actionability | Provides fully executable bash commands and JSON payloads for every operation—posting reviews, resolving threads, replying to comments, and deleting misplaced comments. All examples are copy-paste ready with clear placeholders. | 3 / 3 |
Workflow Clarity | The 'Responding to PR Feedback' section provides a clear decision workflow (fixed → resolve; not fixing → reply with explanation). The line number gotchas section includes a verification step and a recovery action (delete misplaced comment). The safety note about showing proposed comments before posting serves as a validation checkpoint. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections with clear headers that enable quick scanning. For a skill of this size (~80 lines), everything is appropriately inline without needing external references, and the structure progresses naturally from basic posting to responding to edge cases. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- athal7/dotfiles
- Commit
03cec9d
- 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.