mcollina/octocat
Handles git and GitHub operations using the gh CLI. Use when the user asks about pull requests (PRs), GitHub issues, repo management, branching, merging, rebasing, cherry-picking, merge conflict resolution, commit history cleanup, pre-commit hook debugging, GitHub Actions workflows, or releases. Covers creating and reviewing PRs, watching CI checks, interactive rebasing, branch cleanup, submodule management, and repository archaeology with git log/blame/bisect.
93
93%
Does it follow best practices?
Impact
Pending
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 an excellent skill description that covers all evaluation dimensions well. It provides comprehensive specific actions, includes a rich set of natural trigger terms users would actually use, explicitly states both what the skill does and when to use it, and is clearly distinguishable from other skills through its focused git/GitHub domain.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating and reviewing PRs, watching CI checks, interactive rebasing, branch cleanup, submodule management, repository archaeology with git log/blame/bisect, cherry-picking, merge conflict resolution, commit history cleanup, pre-commit hook debugging, and GitHub Actions workflows. | 3 / 3 |
Completeness | Clearly answers both 'what' (handles git and GitHub operations using gh CLI, with specific actions listed) and 'when' (explicit 'Use when the user asks about...' clause with comprehensive trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'pull requests', 'PRs', 'GitHub issues', 'branching', 'merging', 'rebasing', 'cherry-picking', 'merge conflict', 'commit history', 'pre-commit hook', 'GitHub Actions', 'releases', 'git log', 'blame', 'bisect'. These are all terms users naturally use when requesting help with git/GitHub tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to git and GitHub operations via the gh CLI, with highly specific triggers like PRs, rebasing, cherry-picking, GitHub Actions, and git bisect. This is a well-defined niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%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, actionable skill with strong workflow clarity and concrete executable examples. Its main weaknesses are minor redundancy (commit signing rules stated twice) and some unnecessary enumeration in the capabilities section that reads more like documentation than instruction. The PR body-file pattern and validation checkpoints are particularly well done.
Suggestions
Remove the duplicate commit signing rules — consolidate into a single section to improve conciseness.
Trim the 'Capabilities' section to only items that require non-obvious guidance; listing standard git features like 'cherry-pick, bisect, worktrees' doesn't add actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary content like the 'When to use' section listing things Claude could infer, and the capabilities section reads partly like a feature advertisement rather than actionable instruction. The commit signing rules are repeated twice (in Instructions and in a dedicated section). | 2 / 3 |
Actionability | Provides concrete, executable commands throughout — specific gh CLI invocations, git rebase workflows with exact flags, the PR body-file pattern with a complete bash example, and precise conflict resolution commands. Guidance is copy-paste ready. | 3 / 3 |
Workflow Clarity | Multi-step processes (interactive rebase, merge conflict resolution, branch cleanup) are clearly sequenced with explicit validation checkpoints, feedback loops for error recovery (abort on rebase, re-check with git status), and the PR workflow includes CI watching and proactive failure fixing. | 3 / 3 |
Progressive Disclosure | Content is reasonably well-organized with clear section headers, but everything is in a single file with no references to supporting documents. The capabilities list and validation checkpoints could benefit from being split out, though for a skill of this size (~80 lines) it's borderline acceptable. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents