github
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
94
Quality
93%
Does it follow best practices?
Impact
98%
1.30xAverage 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 an excellent skill description that hits all the marks. It provides specific concrete actions, uses natural trigger terms that users would actually say, explicitly states both what the skill does and when to use it with numbered scenarios, and clearly distinguishes itself from related skills with explicit exclusions. The 'NOT for' section is particularly valuable for reducing false positive matches.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'issues, PRs, CI runs, code review, API queries' and elaborates with 'checking PR status or CI', 'creating/commenting on issues', 'listing/filtering PRs or issues', 'viewing run logs'. | 3 / 3 |
Completeness | Clearly answers both what ('GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries') and when with explicit numbered triggers ('Use when: (1) checking PR status or CI, (2) creating/commenting on issues...'). Also includes helpful 'NOT for' exclusions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'GitHub', 'gh', 'issues', 'PRs', 'CI', 'code review', 'PR status', 'run logs' - these are all terms users naturally use when working with GitHub. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on 'gh CLI' operations with clear boundaries. The 'NOT for' section explicitly distinguishes from browser tooling and bulk scripting, reducing conflict risk with other 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 strong, well-crafted skill that provides comprehensive gh CLI coverage with excellent actionability and conciseness. The clear 'When to Use' and 'When NOT to Use' sections effectively scope the skill. Minor improvement could be made by adding validation steps for destructive operations like merging PRs or closing issues.
Suggestions
Add a validation checkpoint before destructive operations (e.g., 'Verify PR checks pass before merging: gh pr checks 55 --repo owner/repo')
Include error handling guidance for common failures like authentication issues or rate limiting
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only actionable commands without explaining what GitHub, PRs, or issues are. Every section earns its place with executable examples. | 3 / 3 |
Actionability | All commands are fully executable and copy-paste ready. Concrete examples with real flags, jq filters, and complete command syntax throughout. | 3 / 3 |
Workflow Clarity | Commands are well-organized by category but lack explicit validation checkpoints or feedback loops. The PR Review Summary template shows a workflow but doesn't include error handling or verification steps. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections progressing from setup to common commands to advanced templates. For a skill of this scope, the organization is appropriate without needing external file references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- trpc-group/trpc-agent-go
- Commit
50ef2f3
- 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.