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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is tdg-personal/github-ops

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Actionable and well-structured gh-CLI guidance with strong command examples, held back by missing validation checkpoints around its destructive/batch operations and minor conciseness redundancy.

Suggestions

Add an explicit validation/feedback step before destructive batch actions — e.g. before auto-closing stale issues, confirm the issue has no recent activity and post a warning comment N days prior; before auto-merging dependency PRs, verify CI is green and the bump is non-major.

De-duplicate the Security Monitoring section: the bash comment '# Review and auto-merge safe dependency bumps' (L130) repeats the bullet on L134 — keep it in one place.

Tighten the intro line 'Manage GitHub repositories with a focus on community health, CI reliability, and contributor experience.' — it states intent without adding executable guidance Claude doesn't already infer from the sections.

Dimension	Reasoning	Score
Conciseness	Mostly efficient sectioned gh commands that assume Claude's competence, but minor padding remains — e.g. the opening line 'Manage GitHub repositories with a focus on community health...' and a duplicated 'Review and auto-merge safe dependency bumps' appearing both as a bash comment (L130) and a bullet (L134).	4 / 5
Actionability	Fully executable, copy-paste-ready gh commands cover the common cases throughout — `gh issue edit --add-label`, `gh pr checks`, `gh run view --log-failed`, `gh release create --generate-notes`, and `gh api ... dependabot/alerts`.	5 / 5
Workflow Clarity	Numbered sequences and a final Quality Gate are present, but destructive/batch operations — 'Auto-close stale issues after 30 days' and 'auto-merge safe dependency bumps' — lack inline validation or feedback loops, so per the rubric cap workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	A single well-organized file with clear section headers (Issue Triage, PR Management, CI/CD, Release, Security, Quality Gate) and no nested references; over 50 lines with no external file split keeps it just below a 5.	4 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that concretely names its capabilities, supplies explicit natural-language triggers, and clearly distinguishes itself from plain git usage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete action areas — 'Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Clearly states what ('GitHub repository operations, automation, and management...') and explicitly when ('Use when the user wants to manage GitHub issues, PRs, CI status, releases...'), satisfying both anchors with concrete triggers.	5 / 5
Trigger Term Quality	The 'Use when' clause covers natural terms users say — 'GitHub issues, PRs, CI status, releases, contributors, stale items' — including synonyms like PRs, with the 'beyond simple git commands' boundary phrase.	5 / 5
Distinctiveness Conflict Risk	Scoped to GitHub operations via the gh CLI 'beyond simple git commands', carving a clear niche with distinct triggers and minimal overlap with a generic git skill.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/github-ops/SKILL.md
Commit: 06c5e11

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.