github

Use the official gh CLI as the GitHub gateway. Prefer gh over raw REST; fall back to gh api <endpoint> only when a verb is missing. gh already speaks the user's authenticated identity, so no tokens are handled in this skill.

Setup check (lazy — do NOT probe every turn)

Do not run gh auth status before each request. Just run the gh command the user asked for — reads go straight through. Only when a command fails map the error to a Setup playbook branch:

• stderr contains command not found: gh → Setup playbook → "gh is not installed".
• stderr contains not logged / gh auth login → Setup playbook → "not authenticated".

If unsure which branch applies, capture stderr and ask the user before proceeding.

Setup playbook (when prerequisites are missing)