Loading...
Loading...
Found 5 Skills
Configure GitHub authentication for Cyrus — gh CLI login and git config for creating pull requests.
Enforces authenticated gh CLI workflows over unauthenticated curl/WebFetch patterns. Use when working with GitHub URLs, API access, pull requests, or issues.
Authenticate to GitHub and fix auth problems — the shared primitive every other github-* skill relies on. Use this BEFORE any create/query when GitHub auth is uncertain, and whenever a GitHub API call misbehaves: a call returns 401 or 403, "gh not logged in" / token missing, results come back empty or from the wrong repo. Covers the two supported methods (gh CLI via `gh auth token`, or GH_TOKEN env var), a one-line PowerShell verify snippet against the repo API, and a 401/403/wrong-repo troubleshooting table. Invoke when someone says "I'm getting a 401 from GitHub", "github-create-issues says no token", "gh auth failing", or "check my GitHub login before we run".
Securely authenticate with GitHub using stored credentials for API operations and git commands
Use this skill for direct work with GitHub: inspecting remote source or repository state, searching hosted code, invoking GitHub CLI (`gh`) commands such as `gh search` and `gh api`, or performing another operation against GitHub. Do not use it for ordinary local Git work unless the user explicitly requests `gh`. Do not use it for tasks limited to viewing or interacting with GitHub in a browser.