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.
95
95%
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 say, 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 would naturally use when requesting help. | 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 non-git 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, 'When to use' overlapping with description) and the lack of progressive disclosure for what is a fairly broad skill covering many git/GitHub topics. The validation checkpoints section is particularly well done with clear feedback loops.
Suggestions
Remove the duplicate commit signing rules — keep only the dedicated section and reference it from Instructions with a brief note
Consider splitting detailed workflows (rebase, conflict resolution, GitHub Actions) into a referenced WORKFLOWS.md to keep SKILL.md as a concise overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the commit signing rules are stated twice (once in Instructions and again in a dedicated section), and the 'When to use' section largely restates what the frontmatter description already covers. Some bullet points like 'Any git command or GitHub workflow question' are vague filler. | 2 / 3 |
Actionability | Provides concrete, executable commands throughout — specific gh CLI invocations with flags, git rebase workflows with exact commands, the PR body-file pattern with a complete bash example, and specific validation commands. Guidance is copy-paste ready. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints and error recovery paths. Interactive rebase, merge conflict resolution, and branch cleanup all have step-by-step flows with verification steps and abort/recovery options. | 3 / 3 |
Progressive Disclosure | Content is reasonably well-organized with clear section headers, but everything is inline in a single file. For a skill of this breadth (PRs, rebasing, conflict resolution, GitHub Actions, submodules, etc.), some content could be split into referenced files. However, the current length is manageable and sections are well-signaled. | 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