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.
Install with Tessl CLI
npx tessl i github:YPares/agent-skills --skill github-pr-workflow95
Does it follow best practices?
Validation for skill structure
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 defines its scope around GitHub Pull Requests using the gh CLI. It provides specific capabilities, natural trigger terms, explicit usage guidance, and a distinct niche that minimizes conflict with other skills. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'fetching PR details, review comments, CI status' and distinguishes 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...'). The 'Use for' clause explicitly states trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'GitHub', 'Pull Requests', 'PR', 'gh CLI', 'review comments', 'CI status'. These cover common variations and natural language users would use when working with PRs. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: GitHub PRs via gh CLI. The combination of 'GitHub', 'Pull Requests', 'gh CLI', and PR-specific terminology (review comments, CI status) creates a distinct trigger profile unlikely to conflict with general git or code review skills. | 3 / 3 |
Total | 12 / 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 skill that efficiently communicates the critical distinction between PR-level and inline comments - knowledge that isn't obvious from gh CLI documentation. The content is actionable with executable commands and useful API references. The main weakness is the incomplete workflow section that cuts off mid-process.
Suggestions
Complete the 'Workflow: Addressing Review Comments' section with remaining steps (e.g., commit, push, verify comments addressed)
Add a validation step to the workflow (e.g., 'Run gh-pr-info again to confirm all comments resolved')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, assuming Claude's competence with git/GitHub. No unnecessary explanations of what PRs are or how GitHub works - jumps straight to the key distinction between comment types and actionable commands. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands throughout. The command table, bash examples, and API endpoints are all immediately executable with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | The 'Workflow: Addressing Review Comments' section is incomplete (cuts off after step 2). While the script and commands are clear, the multi-step workflow for addressing comments lacks completion and validation checkpoints. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Key Concepts, Scripts, Common Commands, API Reference, Workflow). For a skill of this size, the structure is appropriate with logical groupings and a helpful table for quick reference. | 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.