skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
mathews-tom/armory109 installs

github

GitHub CLI operations via `gh` for issues, PRs, Actions, releases, and REST/GraphQL API with `--json`/`--jq` parsing. Triggers on: "create an issue", "submit a PR", "check CI status", "why did CI fail", "merge a PR", or pasted GitHub URLs.

How do I install this agent skill?

npx skills add https://github.com/mathews-tom/armory --skill github
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides comprehensive documentation and command templates for using the GitHub CLI (gh) to manage repositories, issues, pull requests, and automation workflows. It follows best practices by encouraging structured JSON output and minimal data transfer using jq. No malicious patterns or security risks were identified beyond the inherent risks associated with processing external data from a public platform.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

GitHub

All GitHub operations use the gh CLI. Prefer --json with --jq for structured, parseable output. Use --repo owner/repo when not inside a git repository with a configured remote. Use --web to open any resource in the browser.

Prerequisites and Auth

Installation

PlatformCommand
macOSbrew install gh
Debian/Ubuntusudo apt install gh
Windowswinget install GitHub.cli

Authentication

gh auth login           # interactive OAuth login
gh auth status          # check current auth and active account

Required OAuth Scopes

ScopeGrants Access To
repoPrivate repos, issues, PRs, commits, status
read:orgOrg membership, team listing
workflowTrigger and manage GitHub Actions workflows
gistCreate and manage gists
delete_repoDelete repositories (not granted by default)
admin:orgManage org settings, teams, members
projectRead/write access to ProjectV2 boards

Add missing scopes without re-authenticating from scratch:

gh auth refresh --scopes repo,read:org,workflow

Reference Routing

User intentLoad
Create/list/view/edit/close issues, add commentsreferences/issues.md
Create/list/view/review/merge/edit/close pull requestsreferences/pull-requests.md
List runs, view logs, trigger/rerun/watch workflows, artifactsreferences/ci-actions.md
Create/fork/clone/view/edit/archive/delete repositoriesreferences/repos.md
Create/list/view/edit/upload/delete releasesreferences/releases.md
Search repos, issues, PRs, code, commitsreferences/search.md
Raw REST/GraphQL via gh api, pagination, rate limitreferences/api.md
GraphQL cost model, bulk queries, mutations, rate limitsreferences/graphql-queries.md
Multi-step workflow recipes (PR lifecycle, CI triage, releases)references/automation-workflows.md
Create/list/view/edit/delete gistsreferences/gists.md
List orgs, teams, membersreferences/orgs.md

Workflow Pattern

  1. Identify user intent from the routing table above.
  2. Load the matching references/<file>.md for command syntax and examples.
  3. Execute the gh command with --repo owner/repo and --json/--jq as needed.
  4. On error, consult the Error Handling table below.

Error Handling

ErrorCauseResolution
HTTP 401 UnauthorizedToken expired or revokedRun gh auth login to re-authenticate
HTTP 403 ForbiddenInsufficient permissions or rate limitedCheck gh auth status for scopes; check gh api rate_limit
HTTP 404 Not FoundRepo does not exist, is private without repo scope, or resource deletedVerify repo name; run gh auth refresh --scopes repo
HTTP 422 Unprocessable EntityInvalid payload — missing required field, validation errorCheck request body fields match API schema
HTTP 429 Too Many RequestsREST rate limit exceeded (5000 req/hr authenticated)Wait for X-RateLimit-Reset timestamp; reduce request frequency
GraphQL rate limit exceededUsed more than 5000 points/hrReduce query complexity or wait; see references/graphql-queries.md
"no git remotes found"Running gh outside a git repo without --repoAdd --repo owner/repo to the command
Insufficient OAuth scopesToken lacks required scope for the operationRun gh auth refresh --scopes scope1,scope2
Duplicate issue/PR titleNot a real error — GitHub allows duplicates, but check before creatingSearch with gh issue list or gh pr list first
Archived repo blocks writesRepo is archived; all write operations failUnarchive with gh repo edit owner/repo --archived=false or use a different repo

Enable debug logging to see raw HTTP requests and responses:

GH_DEBUG=api gh pr list --repo owner/repo

Calibration Rules

  1. Prefer --json over parsing text output. Text output formats are unstable across gh versions. Always use --json field1,field2 to get machine-readable output.
  2. Use --jq to minimize output before processing. Filter at the source rather than piping large JSON blobs to external tools. --jq runs server-side and reduces data transferred.
  3. Prefer higher-level commands over raw API. Use gh issue create instead of gh api repos/.../issues -X POST. High-level commands handle auth, pagination, and error formatting automatically.
  4. Use --repo consistently when outside a git directory. Never rely on implicit repo detection in scripts or CI environments. Always pass --repo owner/repo explicitly.
  5. Use GraphQL only for nested or bulk data. For single-resource fetches and mutations with simple payloads, REST is faster to write, easier to debug, and predictable under rate limits.

Limitations

  • Network required — all gh commands require internet access; no offline mode.
  • GraphQL point budget — 5000 points/hr for authenticated users. Complex queries with high first/last values consume points faster. See references/graphql-queries.md.
  • Secrets are write-only — gh secret set works, but there is no gh secret get. Secret values cannot be retrieved after creation.
  • Org admin operations — managing org settings, teams, and SAML requires the admin:org scope, which is not granted by default.
  • Artifact retention — workflow artifacts are retained for 90 days by default. Expired artifacts cannot be downloaded.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/mathews-tom/armory/github">View github on skillZs</a>