CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

github-ops

Operates GitHub via gh CLI and REST/GraphQL — PRs, issues, Actions, self-hosted Runner inventory/capacity, repos, collaborators, org permissions, 2FA — with explicit target, authorization, and independent readback. Use when a write reports success but state didn't change, or choosing gh/REST/GraphQL/UI-only. Not for local Git recovery (use git-safety-net), maintainer PR review (use github-review-pr), or upstream contribution (use github-contributor).

Quality

87%

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

85%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 exceptionally actionable and well-sequenced operations contract with excellent progressive disclosure — every command is executable, verification is built into every step, and detail is properly split across an intact reference bundle. The main drag is conciseness: the checked_gh wrapper mechanics and an incident-attribution aside add substantial length that a competent reader doesn't need inline.

Suggestions

Move the checked_gh.py internal behavior details (environment scrubbing, host-operand conflict rules, rejected command classes) into the script's docstring or a short reference file, keeping only the invocation syntax and the actor-check guarantee in SKILL.md.

Trim or relocate the incident-attribution paragraph about the 'ChatGPT execution account' — it addresses a different tool's incident forensics and adds context cost without supporting this skill's operating contract.

Consolidate the repeated identity/recheck rules in step 2 ('Switching account, credential, host or interface invalidates earlier identity evidence. Recheck before the next write; do not reuse a prior session's pass') with the earlier bind-identity instructions to remove redundancy.

DimensionReasoningScore

Conciseness

The body avoids explaining basic concepts and is dense with operational rules, but sections could be tightened: step 2 devotes ~40 lines to the checked_gh wrapper's internal behavior ("removes inherited GH_REPO and alternate token variables from the child, and rejects conflicting host operands") that belongs in the script's own documentation, and the incident-attribution paragraph ("the ChatGPT execution account") is off-topic for this skill's core contract. This lands at 'mostly efficient but some unnecessary explanation or could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

Guidance is fully executable: concrete commands with exact flags and --json field lists ("gh repo view HOST/OWNER/REPO --json nameWithOwner,visibility,isPrivate,viewerPermission,url"), copy-paste-ready checked_gh.py invocations with real argument shapes, a fill-in delta-preview template, and a ready-to-run read-only quick reference. Specific evidence requirements per mutation type (e.g. "Secret/variable change | Metadata and consumer behavior, never secret value disclosure") cover the common cases.

5 / 5

Workflow Clarity

The universal operating contract is an explicitly sequenced 8-step process (classify → bind identity → preview delta → choose interface → mutate once → independent readback → report outcome → scoped authentication) with strong validation checkpoints and feedback loops: "After a timeout or 5xx, read back first to determine whether the first request landed", "If readback differs, report failed/no-op or partially applied… and keep recovery available", and bounded polling with a pending state. This matches the anchor for clear sequence with explicit validation and error-recovery loops, including for the destructive/batch operations this skill covers.

5 / 5

Progressive Disclosure

SKILL.md is a well-structured overview with a task→reference routing table pointing to 11 one-level-deep reference files (all of which exist in references/), a bundled script clearly linked, and an anchor link (references/pr_operations.md#merging-prs) that resolves to a real '### Merging PRs' section. Operation-specific detail is appropriately deferred while the cross-cutting contract stays inline; navigation by task is easy.

5 / 5

Total

18

/

20

Passed

Description

83%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, third-person description with explicit positive and negative trigger guidance and excellent sibling-skill disambiguation. Its only weakness is that the explicit "Use when" clause captures edge-case triggers rather than the mainline "performing GitHub operations" scenario, and a few common synonyms (pull requests, merge, branches, CI) are missing.

Suggestions

Extend the 'Use when' clause to cover the primary case directly, e.g. 'Use when creating, merging, or reviewing PRs, managing issues, Actions runs, or repository/organization settings on GitHub'.

Add a few natural synonyms users actually say — 'pull requests', 'merge', 'branches'/'branch protection', 'CI' — alongside the existing PRs/Actions/repos terms.

DimensionReasoningScore

Specificity

Enumerates concrete capability areas — "PRs, issues, Actions, self-hosted Runner inventory/capacity, repos, collaborators, org permissions, 2FA" — plus the concrete mechanisms "gh CLI and REST/GraphQL" and "explicit target, authorization, and independent readback", giving comprehensive coverage of the domain in third person. Not 4: coverage spans the full GitHub-operations surface with named operations and interfaces rather than having minor gaps.

5 / 5

Completeness

Both parts are explicit: the what ("Operates GitHub via gh CLI and REST/GraphQL…") and a "Use when…" clause ("Use when a write reports success but state didn't change, or choosing gh/REST/GraphQL/UI-only"), plus negative scoping. Not 5: the explicit when-clause covers secondary triggers (failed-write verification, interface choice) while the primary trigger — performing everyday GitHub operations like creating a PR or merging — is only implicit in the what-list, so the when-guidance could be more directly specific.

4 / 5

Trigger Term Quality

Includes natural terms users would say — "PRs", "issues", "Actions", "repos", "collaborators", "org permissions", "2FA", "gh CLI" — and trigger phrases like "a write reports success but state didn't change". Not 5: common variants such as "pull requests" spelled out, "merge", "branches", "branch protection", "CI/workflow runs", and "GitHub" itself are absent, leaving a few natural entry phrases uncovered.

4 / 5

Distinctiveness Conflict Risk

Claims a clear niche (GitHub-hosted state operations) and explicitly diverts adjacent cases — "Not for local Git recovery (use git-safety-net), maintainer PR review (use github-review-pr), or upstream contribution (use github-contributor)" — minimizing conflict with the most likely neighboring skills. Not 4: the explicit negative triggers and interface boundary (gh/REST/GraphQL/UI) make overlap risk minimal, not merely minor.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

daymade/claude-code-skills

Path

github-ops/SKILL.md

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.