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.
87
82%
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 (PRs, issues, repos, workflows, API) without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating/viewing/merging PRs, managing issues, querying API endpoints, handling GitHub workflows. Also mentions gh CLI and GitHub API as specific tools. | 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 git or other platform skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%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 reference skill with excellent actionability—every section provides real, executable commands. Its main weaknesses are redundancy (the Quick Reference duplicates earlier examples, and the Resources section re-describes already-linked references) and the lack of multi-step workflows with validation checkpoints for operations like PR creation-to-merge flows. Trimming duplicate content and adding sequenced workflows would significantly improve it.
Suggestions
Remove or consolidate the 'Quick Reference' section and 'Resources' descriptions to eliminate redundancy with the inline examples and 📚 links already provided.
Add at least one multi-step workflow with validation checkpoints, e.g., a PR creation-to-merge flow: create PR → verify checks pass → request review → merge, with explicit validation at each step.
Remove the 'When to Use This Skill' section—this duplicates the skill description metadata and wastes tokens on information Claude doesn't need.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'When to Use This Skill' (which restates the description) and the 'Resources' section that redundantly describes what each reference file contains after already linking to them inline. The 'Quick Reference' section also largely duplicates commands already shown above. However, the core content is reasonably efficient with executable examples. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready bash commands throughout. Every operation has concrete examples with real flags and arguments. The PR title convention with NOJIRA/JIRA patterns is a specific, actionable detail that adds real value. | 3 / 3 |
Workflow Clarity | Individual commands are clear, but there are no multi-step workflows with validation checkpoints. For example, the PR creation flow doesn't include verifying the PR was created, checking CI status, and then proceeding to merge. Operations are presented as isolated commands rather than sequenced workflows with feedback loops. | 2 / 3 |
Progressive Disclosure | The skill references five separate reference files with clear descriptions and loading guidance, which is good structure. However, since no bundle files are provided, we cannot verify these references exist. Additionally, the 'Resources' section at the bottom redundantly re-describes each reference file that was already linked inline with 📚 markers, and the main file itself is somewhat long with content that could be pushed to references (e.g., the full authentication and output format sections). | 2 / 3 |
Total | 9 / 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
- daymade/claude-code-skills
- Commit
bbf87f3
- 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.