# Check Github CLI

> Check Github CLI is an Agent Skill for apps & automation published in the blockscout/frontend repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure GitHub CLI (gh) is installed and authenticated before running gh commands; guide the user to configure it if not

- Skill name: `check-github-cli`
- Category: [Apps & Automation](https://www.openparable.com/skill/apps-automation/1)
- Source: https://github.com/blockscout/frontend/blob/HEAD/.agents/skills/check-github-cli/SKILL.md
- Repository: blockscout/frontend (289 GitHub stars when collected)

## SKILL.md

# Check GitHub CLI Availability

Use this skill whenever a workflow or command requires the GitHub CLI (`gh`). Before running any `gh` commands:

1. **Check installation and auth**: Run `gh auth status`. If it reports "not logged in" or the command is not found:
   - **If `gh` is not installed**: Ask the user to install it (e.g. `brew install gh` on macOS, or see [GitHub CLI](https://cli.github.com/)) and then authenticate.
   - **If `gh` is installed but not configured**: Ask the user to configure it themselves. Provide these instructions to help them:
     - Run `gh auth login` and follow the prompts (choose HTTPS or SSH, authenticate via browser or token).
     - Ensure the account has the permissions needed for the operation (e.g. read access to the repository, or read/write if the task requires it).
   - Do not attempt to authenticate on the user's behalf; only guide them with the commands and link to [GitHub CLI authentication docs](https://cli.github.com/manual/gh_auth_login).
2. **If `gh auth status` succeeds**: Proceed with the steps that require `gh`.

Other skills that depend on `gh` (e.g. get-checks-status) should instruct the agent to ensure GitHub CLI is ready first by following this skill.

---

Source: https://www.openparable.com/skill/apps-automation/check-github-cli (OpenParable). Cite the canonical URL above.
