odyssey4me/github
Create and manage GitHub issues, pull requests, workflows, and repositories using the gh CLI. Use when asked to open a PR, merge a pull request, check repo actions, list issues, create a branch, or manage GitHub projects.
68
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 what the skill does (GitHub operations via gh CLI) and when to use it (with explicit trigger phrases). It uses third person voice, lists concrete actions, and includes natural user language. It serves as a good example of a well-crafted skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: create/manage issues, pull requests, workflows, and repositories using the gh CLI. The tool (gh CLI) is explicitly named. | 3 / 3 |
Completeness | Clearly answers both 'what' (create and manage GitHub issues, PRs, workflows, repositories using gh CLI) and 'when' (explicit 'Use when...' clause with specific trigger scenarios like opening PRs, merging, checking actions, listing issues). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'open a PR', 'merge a pull request', 'check repo actions', 'list issues', 'create a branch', 'manage GitHub projects'. These are phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to GitHub operations via the gh CLI, which is a distinct niche. The mention of specific GitHub entities (issues, PRs, workflows, actions) and the gh CLI tool makes it unlikely to conflict with general git or code skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides comprehensive, executable command references for GitHub CLI operations but suffers significantly from verbosity — it essentially reproduces the gh CLI manual rather than adding only what Claude doesn't already know. The workflow examples are a strength, showing practical multi-step scenarios with some verification, but the bulk of the content (direct gh commands, configuration, troubleshooting, aliases) is redundant information Claude can access via `gh --help`.
Suggestions
Remove or drastically reduce the 'Commands (Direct gh Usage)' section — Claude already knows gh CLI commands and can use `gh <command> --help`. Focus only on the wrapper script usage and the read/write distinction.
Move the Advanced Usage, Configuration, Troubleshooting, and Aliases sections into a separate reference file to keep SKILL.md as a concise overview.
Add explicit error handling guidance to workflows involving destructive operations (e.g., what to do if `gh pr merge` fails due to conflicts or failed checks).
Remove the Summary section which redundantly restates the content, and trim the Official Documentation links which Claude can find on its own.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is very verbose, essentially duplicating the gh CLI's own help documentation. The direct gh usage sections (Issues, PRs, Workflows, Repositories, Search) repeat commands already shown in the wrapper script section. Configuration, troubleshooting, aliases, and official documentation links are all things Claude already knows or can discover via `gh --help`. The Summary section redundantly restates what was already covered. | 1 / 3 |
Actionability | All commands are concrete, copy-paste ready bash commands with specific examples. The script usage, direct gh commands, and workflow examples all provide executable guidance with real flags and arguments. | 3 / 3 |
Workflow Clarity | The Examples section shows multi-step workflows (Daily PR Review, Create Issue and Link PR, Monitor CI Pipeline) with some verification steps ('Verify approval was recorded', 'Verify PR was created'). However, there are no explicit error handling or feedback loops for destructive operations like merging PRs or closing issues — what to do if merge fails, if there are conflicts, etc. | 2 / 3 |
Progressive Disclosure | References to permissions.md and common-workflows.md are well-signaled, but the main SKILL.md contains far too much inline content that could be split out (the entire direct gh usage reference section, advanced usage, configuration, troubleshooting). The file is a near-monolithic reference rather than a concise overview pointing to details. | 2 / 3 |
Total | 8 / 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