How do I install the CLI Gh skill?

Run npx skillmds add om-scogo/cli-gh in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CLI Gh safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CLI Gh?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CLI Gh free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CLI Gh?

om-scogo (@om-scogo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CLI Gh by om-scogo — Agent Skill

Name: CLI Gh
Rating: 4.2 (5 reviews)
Author: om-scogo

CLI Gh

Use for GitHub CLI automation: repository reads, workflow runs, search, codespaces, releases, configuration, or gh command syntax. Use yeet for contribution writes to PRs, issues, comments, or discussions.

om-scogo a6e4931 4 files · 10.6 KB Updated Sep 9, 2026 0 repo stars

File contents

GitHub CLI

Route GitHub CLI work through current gh help and load only the reference for the active task.

Boundary with `yeet`

Use yeet when the requested outcome is to create or update a pull request, issue, issue comment, or discussion. yeet owns semantic analysis, repository templates, Paul's writing voice, idempotency, and direct posting. Use this skill for read-only GitHub inspection, command syntax, searches, workflow operations, codespaces, releases, configuration, and other GitHub automation.

Authority

Read and inspect without confirmation.
Execute reversible or ordinary GitHub writes only when the user explicitly requested that outcome.
Never delete repositories, releases/assets, workflow runs/caches, secrets/variables, keys, codespaces, extensions, or gists.
Label deletion is the sole destructive exception: show the target repo, exact labels, commands, and issue/PR impact, then require approval in a subsequent message before gh label delete ... --yes.
Route repository renames through repo-rename so GitHub and local continuity change together.

Workflow

Resolve the repository explicitly when cwd is ambiguous. Let the first required read-only command validate authentication; run gh auth status only for auth diagnosis.
Inspect gh <command> <subcommand> --help for the installed version before relying on flags or JSON fields. Prefer --json plus --jq for machine-readable results.

Load only the relevant reference:

Task	Reference
Workflow runs, checks, logs	`references/workflows-actions.md`
Releases	`references/releases.md`
Search	`references/search.md`
JSON fields and jq	`references/json-output.md`
Labels	`references/labels.md`
Codespaces	`references/codespaces.md`
Discussions syntax (not authored contribution workflow)	`references/discussions.md`
Gists	`references/gists.md`
Aliases, API, extensions, org/projects, secrets, rulesets	`references/advanced-features.md`
Reusable automation patterns	`references/automation-workflows.md`
Failures and auth/rate limits	`references/troubleshooting.md`

Preview commands that have broad write scope. After a requested write, fetch the resulting resource and report its URL or stable identifier.

Completion requires the requested GitHub state or data plus command/output evidence. On a partial or ambiguous write failure, check whether the resource changed before retrying.

---name: cli-ghdescription: Use for GitHub CLI automation: repository reads, workflow runs, search, codespaces, releases, configuration, or gh command syntax. Use yeet for contribution writes to PRs, issues, comments, or discussions.--- # GitHub CLI Route GitHub CLI work through current `gh` help and load only the reference for the active task. ## Boundary with `yeet` Use `yeet` when the requested outcome is to create or update a pull request, issue, issue comment, or discussion. `yeet` owns semantic analysis, repository templates, Paul's writing voice, idempotency, and direct posting. Use this skill for read-only GitHub inspection, command syntax, searches, workflow operations, codespaces, releases, configuration, and other GitHub automation. ## Authority - Read and inspect without confirmation. - Execute reversible or ordinary GitHub writes only when the user explicitly requested that outcome. - Never delete repositories, releases/assets, workflow runs/caches, secrets/variables, keys, codespaces, extensions, or gists. - Label deletion is the sole destructive exception: show the target repo, exact labels, commands, and issue/PR impact, then require approval in a subsequent message before `gh label delete ... --yes`. - Route repository renames through `repo-rename` so GitHub and local continuity change together. ## Workflow 1. Resolve the repository explicitly when cwd is ambiguous. Let the first required read-only command validate authentication; run `gh auth status` only for auth diagnosis. 2. Inspect `gh <command> <subcommand> --help` for the installed version before relying on flags or JSON fields. Prefer `--json` plus `--jq` for machine-readable results. 3. Load only the relevant reference: | Task | Reference | | --------------------------------------------------------- | ------------------------------------ | | Workflow runs, checks, logs | `references/workflows-actions.md` | | Releases | `references/releases.md` | | Search | `references/search.md` | | JSON fields and jq | `references/json-output.md` | | Labels | `references/labels.md` | | Codespaces | `references/codespaces.md` | | Discussions syntax (not authored contribution workflow) | `references/discussions.md` | | Gists | `references/gists.md` | | Aliases, API, extensions, org/projects, secrets, rulesets | `references/advanced-features.md` | | Reusable automation patterns | `references/automation-workflows.md` | | Failures and auth/rate limits | `references/troubleshooting.md` | 4. Preview commands that have broad write scope. After a requested write, fetch the resulting resource and report its URL or stable identifier. Completion requires the requested GitHub state or data plus command/output evidence. On a partial or ambiguous write failure, check whether the resource changed before retrying.

Frequently asked questions