How do I install the Connect Github Repo skill?

Run npx skillmds@latest add darikzen/connect-github-repo in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Connect Github Repo safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Connect Github Repo?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Connect Github Repo free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Connect Github Repo?

Darikzen (@darikzen) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Connect Github Repo by darikzen — Agent Skill

Name: Connect Github Repo
Author: Darikzen

File contents

Connect GitHub Repo (Session-Only)

Use when the user asks to connect to a GitHub repo for this session only, possibly with a different GitHub account than other sessions. Do not explore auth paths first — run the script immediately.

Fast path (do this first)

Parse the repo from the user's URL or owner/repo slug.
Run the connect script (no PAT, device login only if needed):

bash "$HOME/.cursor/skills/my-cursor-skills/connect-github-repo/scripts/connect.sh" "<owner/repo-or-url>" "<workspace-root>"

Use the current workspace directory for <workspace-root> (often /workspace in Cloud Agents, or the project root locally).

If device login is required, tell the user immediately in your first reply:
- Link: https://github.com/login/device
- The one-time code printed by the script
- Which GitHub account to sign in as (if they named one)
After they confirm, re-run the script or verify with gh auth status and git push --dry-run origin HEAD.
Do not modify repo files unless the user asks.

Switching GitHub accounts mid-session

gh auth logout -h github.com
bash "$HOME/.cursor/skills/connect-github-repo/scripts/connect.sh" "<repo>" "<workspace-root>"

Each Cloud Agent session is a fresh VM — credentials do not persist across runs. Local sessions persist until logout.

Why not Cursor long-term GitHub integration?

Cursor's managed GitHub token only applies when an agent is started from a connected repo. For ad-hoc "work on this repo this session" requests (especially with varying accounts), gh device login is the right tool: no PAT, no dashboard setup, ~30 seconds of user action.

Do not waste time on

Searching for GitHub tokens in environment variables (there aren't any for github.com in New Project sessions)
Probing the Cursor agent socket for GitHub credentials
Editing README or other repo files during connect
Setting up Cloud Agent environments or repositoryDependencies unless the user explicitly asks for long-term setup

Verify success

gh auth status -h github.com
git remote -v
git push --dry-run origin HEAD

Report: connected account, repo slug, push access yes/no.

---name: connect-github-repodescription: Quickly connect a session to a GitHub repo using gh device login (no PAT). Use when the user asks to connect, clone, or work with a specific GitHub repo in this session only, possibly with a different GitHub account.---# Connect GitHub Repo (Session-Only)Use when the user asks to connect to a GitHub repo for **this session only**, possibly with a **different GitHub account** than other sessions. Do not explore auth paths first — run the script immediately.## Fast path (do this first)1. Parse the repo from the user's URL or `owner/repo` slug.2. Run the connect script (no PAT, device login only if needed):```bashbash "$HOME/.cursor/skills/my-cursor-skills/connect-github-repo/scripts/connect.sh" "<owner/repo-or-url>" "<workspace-root>"```Use the current workspace directory for `<workspace-root>` (often `/workspace` in Cloud Agents, or the project root locally).3. If device login is required, tell the user **immediately** in your first reply: - Link: https://github.com/login/device - The one-time code printed by the script - Which GitHub account to sign in as (if they named one)4. After they confirm, re-run the script or verify with `gh auth status` and `git push --dry-run origin HEAD`.5. Do **not** modify repo files unless the user asks.## Switching GitHub accounts mid-session```bashgh auth logout -h github.combash "$HOME/.cursor/skills/connect-github-repo/scripts/connect.sh" "<repo>" "<workspace-root>"```Each Cloud Agent session is a fresh VM — credentials do not persist across runs. Local sessions persist until logout.## Why not Cursor long-term GitHub integration?Cursor's managed GitHub token only applies when an agent is **started from** a connected repo. For ad-hoc "work on this repo this session" requests (especially with varying accounts), **gh device login** is the right tool: no PAT, no dashboard setup, ~30 seconds of user action.## Do not waste time on- Searching for GitHub tokens in environment variables (there aren't any for github.com in New Project sessions)- Probing the Cursor agent socket for GitHub credentials- Editing README or other repo files during connect- Setting up Cloud Agent environments or `repositoryDependencies` unless the user explicitly asks for long-term setup## Verify success```bashgh auth status -h github.comgit remote -vgit push --dry-run origin HEAD```Report: connected account, repo slug, push access yes/no.

Frequently asked questions

Connect Github Repo