tdg-personal/github-ops
GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git commands.
85
85%
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 a strong skill description that covers all key dimensions well. It lists specific capabilities, includes natural trigger terms users would use, explicitly states when to use it, and clearly differentiates itself from related skills like basic git operations. The 'beyond simple git commands' qualifier is particularly effective for reducing conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: issue triage, PR management, CI/CD operations, release management, security monitoring, and specifies the tool used (gh CLI). | 3 / 3 |
Completeness | Clearly answers both what (issue triage, PR management, CI/CD operations, release management, security monitoring using gh CLI) and when (explicit 'Use when...' clause listing specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'GitHub issues', 'PRs', 'CI status', 'releases', 'contributors', 'stale items', 'GitHub operational task', 'gh CLI', and the distinction from 'simple git commands' helps clarify scope. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly distinguishes itself from generic git skills by specifying 'beyond simple git commands' and focusing on GitHub-specific operations via gh CLI. The niche is well-defined and unlikely to conflict with general git or code 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, actionable skill with excellent gh CLI command coverage across multiple GitHub operations domains. Its main weaknesses are the lack of explicit validation/feedback loops in workflows (particularly around release and triage verification) and some verbosity in explaining concepts Claude already understands. The content would benefit from tighter prose and explicit checkpoint steps.
Suggestions
Add explicit validation steps within workflows—e.g., after applying labels, verify with `gh issue view <number> --json labels`; before creating a release, verify CI status with `gh run list --branch main --status completed --limit 1`.
Trim explanatory text Claude already knows, such as 'Read the issue title, body, and comments' and the definitions of priority levels (critical = breaking/security, etc.)—instead just list the label names.
Consider splitting security monitoring and stale management policies into referenced sub-files to improve progressive disclosure for this longer skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary guidance Claude already knows (e.g., explaining what issue types mean, basic triage logic like 'read the issue title, body, and comments'). The stale policy dates and some explanatory text could be tightened. | 2 / 3 |
Actionability | Provides concrete, executable gh CLI commands throughout every section. Commands are copy-paste ready with clear parameters, and each workflow section pairs instructions with specific bash examples. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced (triage, PR management, CI debugging, release), but validation checkpoints are weak. The Quality Gate section at the end is a checklist but lacks explicit feedback loops—e.g., no 'verify labels were applied' step after triaging, no validation that CI is actually green before creating a release, and CI investigation says to check flaky vs real but doesn't define how to verify the distinction. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a monolithic file with no references to external files for detailed topics like security monitoring policies, stale management automation, or changelog generation templates. For a skill this long (~120 lines), some content could be split out. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents