github-ops

An agent skill by daymade, from daymade/claude-code-skills. Tags: access-control, api, automation, deployment, github.

What it does

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.

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add daymade/claude-code-skills --skill github-ops

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/daymade/claude-code-skills
cp -r claude-code-skills/github-ops ~/.claude/skills/github-ops

Safety box score

Grade D, elevated risk: 63 of 100 risk points, rated 2026-09-22. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.

This skill is a broad GitHub control surface: it can read and mutate repositories, PRs, issues, workflows, collaborators, organization settings, and GHCR images through `gh`/API calls. The main risks are destructive or externally visible GitHub actions, secret handling, and organization-level permission changes; the local-machine impact is comparatively limited.

Category levels, from 0 (none) to 3 (high)
Category	Level	Why
Code & shell execution	2 (moderate)	It runs shell-level GitHub tooling and related commands such as `gh`, `git push`, `docker buildx build --push`, and `curl`, so it can execute commands but not arbitrary opaque binaries.
Network access	3 (high)	It is designed to send requests to GitHub/GHCR and includes remote operations like `gh api`, workflow dispatches, and `curl -s "https://api.github.com/..."`, so data leaves the machine routinely and broadly.
Filesystem reach	1 (low)	Local effects are mostly bounded to the working tree and temp files, e.g. `docker_config=$(mktemp -d)` and `metadata_file=$(mktemp)`, with no system-path edits or wide recursive cleanup beyond that temp dir.
Secrets & credentials	3 (high)	It explicitly handles authentication material (`gh auth token --hostname "$host" \| docker ... login ghcr.io`) and can manage GitHub secrets/variables, which makes credential exposure or misuse high impact.
Privilege & persistence	2 (moderate)	It can change GitHub permission and settings surfaces (`collaborators`, teams, base permissions, branch protection, organization 2FA) and also adjusts local Git/CLI config, though it does not require sudo or install services.
Instruction hijack surface	1 (low)	The text repeatedly pushes the agent to proceed once a write is deemed authorized, e.g. `Do not add a ceremonial second confirmation` and `without another approval gate`, which is a mild prompt-manipulation risk.
Irreversible actions	3 (high)	It can create, merge, close, comment on, transfer, archive, delete, and publish GitHub-hosted state, plus trigger/cancel workflow runs and enforce org settings, so the external blast radius is very large.
Transparency	0 (none)	All shipped files are plain Markdown reference text and command snippets; there are no binaries, hidden payloads, or runtime-decoded code.

Before installing

Read `SKILL.md` and `references/repository_operations.md` if you do not want a skill that can delete, transfer, or change repository visibility.
If you use organization repos, review `references/organization_access_and_settings.md`; it can change collaborator access and 2FA enforcement.
Check whether piping `gh auth token` into Docker login is acceptable in your environment before enabling GHCR publishing.
Confirm you are comfortable granting an agent authority to create/merge/close PRs, comment publicly, and trigger or cancel workflows.

Rated 2026-09-22 by an automated review of 10 files from the skill's repository.

Source

Repository: daymade/claude-code-skills (all skills from this repository)
Path: github-ops/SKILL.md
Branch: main
Updated: 2026-09-20

gh-cli — Enforces authenticated gh CLI workflows over unauthenticated curl, WebFetch, and MCP fetch patterns.
agents-connect — Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies.
agents-deploy — Use when deploying your agent to AWS, or when a deploy has failed.
aws-auth — Adds user authentication to web and mobile apps with Amazon Cognito (user pools and identity pools) and the AWS Amplify client auth libraries.
aws-deployment — Configures CI/CD pipelines using AWS CodePipeline, CodeBuild, CodeDeploy, CodeConnections, and CodeArtifact.
aws-secrets-manager — Secret safety for AWS Secrets Manager, secret management, credentials, API keys, tokens, and passwords.