Setup

Skill Nige-l/claude-github-helpers/skills/setup

Check and install the gh CLI, authenticate with GitHub, and verify issue access. Use when user asks to set up the plugin, or when tools fail with auth or missing-dependency errors.From its SKILL.md

Install

npx -y skills add Nige-l/claude-github-helpers --skill setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, as published. Nobody here has run it

/github-helpers:setup

Guide the user through installing and authenticating the GitHub CLI for the github-helpers plugin.

Steps

1. Check if gh is installed

command -v gh && gh --version

If found: proceed to step 2.
If missing: proceed to step 3 to install it.

2. Check authentication status

gh auth status

If authenticated (no error): proceed to step 4.
If not authenticated (You are not logged into any GitHub hosts): proceed to step 3b.
If token expired or invalid: proceed to step 3b.

3. Install or re-authenticate

3a. Install gh CLI (if missing)

Check which package manager is available and install:

Distro	Check	Install command
Debian/Ubuntu	`command -v apt`	`sudo apt update && sudo apt install -y gh`
Fedora	`command -v dnf`	`sudo dnf install -y gh`
Arch	`command -v pacman`	`sudo pacman -S --noconfirm github-cli`
openSUSE	`command -v zypper`	`sudo zypper install -y gh`

Tell the user the exact command and ask for confirmation before running it (requires sudo).

After install, verify:

gh --version

3b. Authenticate

Explain to the user that authentication requires an interactive login and ask them to run this command in their terminal:

gh auth login

Select GitHub.com, HTTPS, and authenticate via browser or token. After they confirm it completed, re-run the auth check:

gh auth status

4. Verify issue access

Run a quick test against a known public repo to confirm tools are working:

gh issue list --repo cli/cli --limit 3 --json number,title,state

If this returns JSON: setup is complete. Report success.
If it returns an error: diagnose based on the error message (auth, network, rate limit) and guide the user accordingly.

Suggest asking Claude to try list_issues on their own repo as a final smoke test.