github-ops
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 communicates both what the skill does and when it should activate. It uses natural trigger terms that users would employ, lists specific concrete actions, and is well-scoped to GitHub operations specifically. The description is concise yet comprehensive, covering the key GitHub domains without being overly verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating/viewing/merging PRs, managing issues, querying API endpoints, handling GitHub workflows. These are clear, actionable capabilities. | 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'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'pull requests', 'PRs', 'issues', 'repositories', 'workflows', 'GitHub API', 'gh CLI', 'merging PRs', 'enterprise'. These are terms users naturally use when requesting GitHub operations. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to GitHub-specific operations via gh CLI and GitHub API. The mention of specific GitHub entities (PRs, issues, workflows, repositories) and tools (gh CLI) creates a distinct niche unlikely to conflict with general code or git skills. | 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 strong actionability and excellent progressive disclosure to reference files. Its main weaknesses are redundancy (Quick Reference duplicates earlier sections, verbose Resource descriptions, 'When to Use' section) and the lack of multi-step workflow sequences with validation checkpoints for common operations like the PR creation-to-merge lifecycle.
Suggestions
Remove or significantly trim the 'When to Use This Skill' section and the verbose 'Resources' descriptions—the inline 📚 references already serve this purpose, and the activation context belongs in frontmatter.
Add a sequenced PR workflow (create → check status → request review → verify checks pass → merge) with explicit validation steps like `gh pr checks 123 --watch` before merging.
Eliminate the Quick Reference section since it largely duplicates commands already shown in Core Operations, or replace the Core Operations examples with just the Quick Reference to avoid redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'When to Use This Skill' (which duplicates the frontmatter description) and the 'Resources' section that verbosely describes each reference file's contents when brief one-liners would suffice. The Quick Reference section also largely duplicates commands already shown above. However, the core operations sections are reasonably lean. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready bash commands throughout. Every operation includes concrete gh CLI syntax with realistic arguments, and the PR title convention is a specific, actionable pattern. The commands cover the full range of common operations. | 3 / 3 |
Workflow Clarity | While individual commands are clear, there are no multi-step workflows with validation checkpoints. For operations like creating and merging PRs (which involve checking CI status, getting reviews, etc.), there's no sequenced workflow. The PR lifecycle is deferred entirely to a reference file. For bulk operations mentioned in references, no validation/feedback loops are shown in the main skill. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The main skill provides a concise overview with executable quick-start commands, then clearly signals five one-level-deep reference files with descriptive summaries and guidance on when to load each. The 📚 inline markers are well-placed throughout the content. | 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.
- Repository
- fernandezbaptiste/claude-code-skills
- Commit
4f0eae8
- 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.