milkywayrules/verasic-skills

verasic-github-cli-init

GitHub CLI auth for local AI agent harnesses — fine-grained PAT in gitignored .github-agent.local, direnv, gh verify. Use when setting up gh for agents, creating GH_TOKEN, wiring GitHub PR/issue/CI workflows per repo, or before any gh command when auth may be missing.

First seen Jul 25, 2026

Installation

$ npx skills add milkywayrules/verasic-skills --skill verasic-github-cli-init

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from milkywayrules/verasic-skills · top by installs.

npx skills add milkywayrules/verasic-skills

Browse all from milkywayrules/verasic-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents cursor

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,069 B
  • docs SUMMARY.md 301 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 10 installs

SKILL.md

Security: see references/scanner-notes.md and upstream SECURITY.md for expected scanner signals and trust model.

Verasic GitHub CLI Init — Local Agent Harness Auth

Workflows

All paths below assume the Cursor install root; installed elsewhere (e.g. .agents/skills/), adjust the prefix — the scripts themselves are install-root-agnostic. /verasic-init runs the bootstrap for you.

Orchestration (Cursor)

Wire GitHub CLI auth for the local AI agent harness on this repo.

Read .cursor/skills/verasic-github-cli-init/references/setup-protocol.md (or .agents/skills/verasic-github-cli-init/references/setup-protocol.md for cursor-hybrid installs), then run from the repository root:

bash .cursor/skills/verasic-github-cli-init/scripts/bootstrap.sh

After bootstrap, tell the user clearly:

  1. Create a fine-grained PAT scoped to this repo (link: https://github.com/settings/tokens?type=beta) — recommended permissions are in the setup protocol.
  2. Copy .github-agent.local.example → .github-agent.local, set GH_TOKEN, run chmod 600 .github-agent.local (never commit).
  3. Run direnv allow if they use direnv.
  4. Verify with bash .cursor/skills/verasic-github-cli-init/scripts/check-gh.sh.

Do not run gh auth login device-flow loops. Do not print or commit token values. Do not run bare gh auth status in chat — use check-gh.sh.

Bootstrap path — wire a repo once:

  1. Read references/setup-protocol.md (in this skill's directory) for secrets tiers and PAT permissions.
  2. From the repo root: bash .cursor/skills/verasic-github-cli-init/scripts/bootstrap.sh (or /verasic-github-cli-init in Cursor, or let /verasic-init do it).
  3. User creates .github-agent.local with GH_TOKEN (never commit).
  4. Verify: bash .cursor/skills/verasic-github-cli-init/scripts/check-gh.sh

Runtime path — before any gh command:

  1. If GH_TOKEN is unset, load credentials without executing env files:
source .cursor/skills/verasic-github-cli-init/scripts/load-gh-env.sh
  1. Use gh with -R "${GH_REPO}" when auto-detection fails.
  2. Never log or commit tokens. Do not run bare gh auth status in agent logs — use check-gh.sh.

Source of truth

The full spec lives in references/setup-protocol.md. The Cursor rule is a thin digest; never duplicate the spec elsewhere.

Hard rules

  • Local agents → .github-agent.local; CI → GitHub Actions; production → secrets manager — never mix tiers.
  • One fine-grained PAT per repo, scoped to that repo only.
  • Never use gh auth login device-flow polling loops for harness setup — use GH_TOKEN.