Menu
Establish secure access for AI agents and VPS nodes to GitHub repos, managing identity conflicts and GitHub First requirements.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Durable knowledge-vault reference for the Prismtek/Buddy talking-host lip-sync workflow.
Configure, extend, or contribute to Hermes Agent.
Use when reviewing betting-model pipelines, sports prediction datasets, backtests, expected value math, and model-risk controls without placing bets.
Use when planning, drafting, repurposing, and promoting content across YouTube, X, and Twitch while keeping posting, DMs, replies, deletions, and account changes approval-gated.
Use when turning approved bookmarks and linked articles into ranked research digests, summaries, and next actions using read-only browser or API adapters.
Use when preparing concise pre-call context briefs from approved notes, prior conversations, public signals, project status, and open questions.
| name | github-access-management |
| description | Establish secure access for AI agents and VPS nodes to GitHub repos, managing identity conflicts and GitHub First requirements. |
| trigger | remote agent access configuration or SSH permission errors (Permission denied, Key already in use). |
This skill governs the process of establishing secure, autonomous access for AI agents and remote VPS nodes to GitHub repositories, especially when dealing with identity conflicts.
Determine if the request is from a specific GitHub user (e.g., TNwkrk) or a generic machine/VPS (e.g., hermes@srv1425557).
Use for repo-specific access not tied to a global user identity.
gh repo deploy-key add <key_file> --repo <owner/repo> --allow-write --title "<Title>"Use when operating under a known GitHub User identity.
gh api /repos/<owner>/<repo>/collaborators/<username> -X PUT -f permission=pushUse when SSH identity conflicts (key is already in use) block deploy keys and users cannot accept invites.
contents:write permissions.https://<token>@github.com/<owner>/<repo>.git.Symptom: HTTP 422: Validation Failed ... key is already in use.
Root Cause: GitHub prohibits a key from being both a User Account Key (global) and a Deploy Key (repo-specific).
Solution: If a key is tied to a user, you cannot use it as a deploy key for another account. Either:
Personal accounts do not support "Teams" (/orgs API calls will 404). Use individual collaborator invites or deploy keys.
git fetch or git ls-remote from the remote node.