gh-pr-inline
Post inline comments on GitHub PRs via gh api
72
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
32%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 concise and identifies a specific capability (posting inline comments on GitHub PRs), but it lacks completeness by omitting explicit trigger guidance. It would benefit from expanded trigger terms covering natural user language and a clear 'Use when...' clause to help Claude select it appropriately.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to add code review comments, leave feedback on specific lines, or post inline PR comments'
Include natural keyword variations users would say: 'pull request', 'code review', 'line comments', 'review feedback', 'PR feedback'
Consider expanding capabilities if applicable, such as 'Post inline comments, reply to review threads, or add suggestions on GitHub PRs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific action ('Post inline comments') and domain ('GitHub PRs') with a tool ('gh api'), but only describes one action rather than multiple concrete capabilities. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'GitHub PRs', 'inline comments', and 'gh api', but misses common variations users might say like 'pull request', 'code review', 'PR comments', or 'review comments'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'inline comments' and 'gh api' specificity helps distinguish it, but 'GitHub PRs' is broad enough to potentially conflict with other GitHub-related skills for PR management, reviews, or general PR operations. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, focused skill that efficiently addresses a specific gap in `gh` CLI functionality. The content is highly actionable with executable examples and avoids unnecessary explanation. The main weakness is the lack of an explicit workflow with verification steps, especially given that misplaced comments are a known issue mentioned in the gotchas.
Suggestions
Add an explicit workflow sequence: 1) Construct JSON, 2) Show proposed comments for approval, 3) Post, 4) Verify placement, 5) Delete/repost if needed
Consider adding a verification step example showing how to fetch and confirm posted comments landed correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No explanation of what GitHub PRs are or how APIs work. Directly addresses the non-obvious limitation of `gh pr review` and provides the solution. | 3 / 3 |
Actionability | Provides complete, copy-paste ready bash commands and JSON structures. The heredoc pattern with `--input -` is executable as-is, and the multi-line comment example shows exact JSON format needed. | 3 / 3 |
Workflow Clarity | While the individual commands are clear, there's no explicit workflow sequence for the full process (get PR info → construct comments → post → verify). The 'Line Number Gotchas' section hints at verification but doesn't integrate it into a clear validate-then-fix loop. | 2 / 3 |
Progressive Disclosure | For a focused, single-purpose skill under 50 lines, the content is well-organized with clear section headers. No need for external references given the scope, and information is logically grouped. | 3 / 3 |
Total | 11 / 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.
- 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.