CtrlK
BlogDocsLog inGet started
Tessl Logo

github-ops

Operates GitHub through gh CLI and the REST/GraphQL APIs with explicit target, authorization, impact preview, and independent readback. Use for pull requests, issues, Actions, repositories, collaborators, teams, organization member privileges, base permissions, 2FA enforcement, repository settings, API automation, parallel or superseded PR convergence, and public or enterprise GitHub. Also use when a GitHub write returned success but the requested state did not change, or when deciding whether a setting is writable through CLI, REST, GraphQL, or only the GitHub UI.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplar operational skill body: concise, fully actionable, with a clearly sequenced workflow that embeds validation/readback checkpoints and routes detail to one-level-deep reference files. It balances safety guidance with token efficiency.

DimensionReasoningScore

Conciseness

Lean, directive operational prose that assumes Claude's competence — it never explains concepts Claude already knows (no 'what is a PR/GitHub') and every line (operating contract, readback table, reporting states) earns its place.

5 / 5

Actionability

Copy-paste-ready commands throughout — `gh auth status --hostname HOST`, `gh repo view ... --json ...`, the quick-reference block, and a concrete readback evidence table mapping each mutation to required acceptance proof.

5 / 5

Workflow Clarity

A clear 7-step universal operating contract (Classify → Bind → Preview → Choose interface → Mutate once → Verify readback → Report) with explicit validation checkpoints, bounded polling, feedback loops, and a four-state honest reporting checklist for destructive/batch operations.

5 / 5

Progressive Disclosure

SKILL.md is a well-signaled overview with a task→reference routing table linking one level deep to 7 real reference files (all present in ./references/); bulk detail is split out and navigation is easy.

5 / 5

Total

20

/

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 highly specific, well-triggered description that explicitly covers what the skill does and when to invoke it, with rich natural keywords and a clear distinct niche. It avoids vague fluff and over-claims entirely.

DimensionReasoningScore

Specificity

Names concrete mechanisms ('Operates GitHub through gh CLI and the REST/GraphQL APIs') plus concrete practices ('explicit target, authorization, impact preview, and independent readback') and enumerates many operational domains, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both: 'what' (operate GitHub via gh CLI/REST/GraphQL with target, authorization, preview, readback) and 'when' via two concrete trigger clauses ('Use for...', 'Also use when a GitHub write returned success but the requested state did not change').

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage users would actually say — 'pull requests', 'issues', 'Actions', 'repositories', 'collaborators', 'teams', '2FA enforcement', 'repository settings', 'public or enterprise GitHub' — including synonym variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche scoped to GitHub-hosted state via gh CLI/APIs with distinctive triggers (2FA enforcement, PR convergence, write-success-but-no-change diagnosis); minimal overlap risk with other skills.

5 / 5

Total

20

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
daymade/claude-code-skills
Reviewed

Table of Contents

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.