connector skills

Setup prompt to copy

---
name: "github"
description: "Use GitHub when the user asks for GitHub or this provider's API."
---

# GitHub

## Purpose
Use GitHub with the user-connected `custom.github` credential (bertybirdbot's classic PAT, `public_repo` scope).

## Tooling
`bin/github` — authenticated CLI (authd surrogates; requests restricted to api.github.com):

- `bin/github info` — show the authenticated user. Safe first call to verify the credential.
- `bin/github repos [--limit N]` — list owned repositories, newest first.
- `bin/github create-repo --name NAME [--description D] [--private]` — create a repository (public by default, initialized with a README).

Notes: the token's `public_repo` scope covers public repos only — private repos and org administration are out of reach by design. Creating a repo is public and effectively permanent; treat it as a consequential action.

## Auth
The credential is already stored; nothing here collects one. Never ask the user to paste a raw token in chat, set a secret environment variable, pass a secret flag, or write an auth file.

A 401 or 403 is a question about the request before it is a question about the key. Check that the credential was attached at all: a request built without the helpers named under Tooling carries nothing, and that looks exactly like a wrong or under-scoped token. Only once a request that did carry the credential is still rejected, call `credentials.request_api_access` with `reconnect` to replace it. The connector is stored as `custom.github`.

## Operating Rules
1. Use this skill when the user asks for GitHub or this provider's API.
2. Restrict authenticated requests to: api.github.com.
3. Do not print, log, or persist raw credentials.
4. If auth is missing or rejected, follow the Auth section rather than asking for a key.

github/SKILL.md from the repo, MIT licence. Read it before pasting. Muse asks before it acts.