github-pr-workflow
Working with GitHub Pull Requests using the gh CLI. Use for fetching PR details, review comments, CI status, and understanding the difference between PR-level comments vs inline code review comments.
90
89%
Does it follow best practices?
Impact
85%
1.06xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its domain (GitHub Pull Requests via gh CLI), lists specific capabilities (PR details, review comments, CI status), and includes an explicit 'Use for...' clause with natural trigger terms. The added detail about distinguishing PR-level comments from inline code review comments adds valuable specificity and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'fetching PR details, review comments, CI status' and clarifies the distinction between 'PR-level comments vs inline code review comments'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (fetching PR details, review comments, CI status, understanding comment types) and 'when' ('Use for fetching PR details, review comments, CI status'). The 'Use for...' clause serves as an explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'GitHub', 'Pull Requests', 'PR', 'gh CLI', 'review comments', 'CI status'. These cover common terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: GitHub PRs via the gh CLI. The specificity around PR-level vs inline code review comments and CI status makes it unlikely to conflict with generic git or code review skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, practical skill that efficiently communicates the critical distinction between PR comment types and provides actionable commands. Its main weaknesses are the truncated workflow section (which cuts off mid-process) and the absence of bundle files to support the referenced script. The content is well-organized and respects Claude's intelligence throughout.
Suggestions
Complete the truncated 'Workflow: Addressing Review Comments' section with all steps including a verification step (e.g., re-running gh-pr-info after pushing fixes to confirm comments are resolved).
Include the gh-pr-info script in the bundle or provide its implementation inline so the skill is self-contained and the referenced tool is available.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what GitHub PRs are or how git works. The critical distinction between PR-level and inline comments is genuinely non-obvious and earns its place. Every section provides actionable reference material without padding. | 3 / 3 |
Actionability | Provides fully executable commands throughout — real gh CLI commands, API endpoint patterns, and a clear script invocation syntax. The commands are copy-paste ready with placeholder conventions that are immediately understandable. | 3 / 3 |
Workflow Clarity | The 'Workflow: Addressing Review Comments' section at the end is truncated after only 2 steps, leaving the multi-step process incomplete. There are no validation checkpoints or feedback loops for verifying that review comments have been properly addressed before pushing changes. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a table for scripts, but the bundle has no supporting files. The script `gh-pr-info` is referenced but not included in the bundle, and there are no references to supplementary documentation for advanced API usage or the script's implementation details. | 2 / 3 |
Total | 10 / 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
- YPares/agent-skills
- Commit
6a552a0
- 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.