check-github-cli

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

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/blockscout/frontend --skill check-github-cli

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

name	check-github-cli
description	Ensure GitHub CLI (gh) is installed and authenticated before running gh commands; guide the user to configure it if not

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

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) 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.
If gh auth status succeeds: Proceed with the steps that require gh.

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

Step-by-step checklist for adding a new NEXT_PUBLIC_* environment variable. Use when introducing any new runtime env var.

Land a finished product task — prune the working files (keep spec.md), then finalize the draft PR into ready-for-review.

Close out review findings — adjudicate each one, fix what deserves fixing, then reply on the PR threads or in the task's review file.

name	check-github-cli
description	Ensure GitHub CLI (gh) is installed and authenticated before running gh commands; guide the user to configure it if not

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

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) 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.
If gh auth status succeeds: Proceed with the steps that require gh.

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