Provides comprehensive GitHub operations using gh CLI and GitHub API. Activates when working with pull requests, issues, repositories, workflows, or GitHub API operations including creating/viewing/merging PRs, managing issues, querying API endpoints, and handling GitHub workflows in enterprise or public GitHub environments.
90
86%
Does it follow best practices?
Impact
95%
1.11xAverage 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 defines its scope (GitHub operations via gh CLI and API), lists specific capabilities (PR management, issues, workflows, API queries), and provides explicit activation triggers. The description effectively distinguishes itself from generic git or code skills by focusing specifically on GitHub platform operations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating/viewing/merging PRs, managing issues, querying API endpoints, and handling GitHub workflows'. Uses third person voice correctly ('Provides', 'Activates'). | 3 / 3 |
Completeness | Clearly answers both what ('comprehensive GitHub operations using gh CLI and GitHub API' with specific actions listed) AND when ('Activates when working with pull requests, issues, repositories, workflows, or GitHub API operations'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'pull requests', 'PRs', 'issues', 'repositories', 'workflows', 'GitHub API', 'gh CLI'. These are terms users naturally use when needing GitHub help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GitHub operations with distinct triggers like 'gh CLI', 'GitHub API', 'PRs', 'merging'. Unlikely to conflict with generic code or git skills due to explicit GitHub focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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-structured skill with excellent actionability and progressive disclosure. The command examples are concrete and executable, and the reference structure is clear. Main weaknesses are some verbosity in introductory sections and lack of explicit validation steps in workflows involving state changes.
Suggestions
Remove or condense the 'When to Use This Skill' section as it largely duplicates information Claude can infer from the skill description
Add validation checkpoints for multi-step operations like PR creation (e.g., 'verify with gh pr view' after creation) and merge workflows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'When to Use This Skill' which duplicates the description, and the 'Overview' section adds little value. The command examples are appropriately terse. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout with copy-paste ready examples. Commands include realistic parameters and cover the full range of common operations with concrete syntax. | 3 / 3 |
Workflow Clarity | Individual commands are clear but multi-step workflows lack explicit sequencing and validation checkpoints. For example, PR creation doesn't mention checking if the PR was created successfully or handling merge conflicts. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references to detailed documentation. Each reference file is clearly described with its purpose and when to load it. | 3 / 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.
4f0eae8
Table of Contents
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.