connect-github-account

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Connect GitHub Account

## Goal

Connect the user's local machine to their GitHub account with SSH. Execute safe local inspection and setup commands when possible, and give clear user-facing instructions for steps that must happen in the GitHub website.

## Core Rules

- Read and apply `../shared/setup-collaboration-workflow.md` before running the GitHub-specific steps below.
- Prefer agent-assisted setup: run local checks and safe setup commands when they do not expose secrets or overwrite user state.
- Never print, copy, upload, summarize, or inspect private key contents.
- Only show public key contents from files ending in `.pub`.
- Never overwrite an existing SSH key.
- If usable SSH keys already exist, ask before generating a new key.
- Ask before changing existing global Git identity values.
- Do not store GitHub passwords, personal access tokens, recovery codes, or two-factor authentication secrets.
- Explain GitHub website steps clearly, because Codex cannot complete them for the user in the browser unless a connected browser tool is explicitly available.
- Treat `Permission denied (publickey)` and `Hi USERNAME! You've successfully authenticated...` as normal verification outputs, not as reasons to expose secrets.
- For every pause or final reply after running commands or waiting for user action, read and follow `../shared/command-response-template.md`.

## Step 1: Inspect Local Prerequisites

Run these local checks first:

```bash
git --version
ssh -V
git config --global --get user.name
git config --global --get user.email
ls -la ~/.ssh
```

Interpret results:

- If `git` is missing, tell the user to install Git before continuing.
- If `ssh` is missing, tell the user to install OpenSSH before continuing.
- If Git identity values are missing, ask for the user's preferred Git commit name and email before setting them.
- If Git identity values already exist, report them and do not change them unless the user asks.
- If `~/.ssh` does not exist, create it with `mkdir -p ~/.ssh && chmod 700 ~/.ssh`.

## Step 2: Choose Or Create An SSH Key

Look for existing public keys:

```bash
ls -la ~/.ssh/*.pub
```

Prefer keys in this order:

1. `id_ed25519.pub`
2. Other `*.pub` keys whose matching private key exists and is not obviously unrelated.
3. A newly generated `ed25519` key.

If an existing suitable key is present, ask whether to use it. If no suitable key exists, ask for the GitHub email address to use as the key comment, then generate:

```bash
ssh-keygen -t ed25519 -C "<github-email>"
```

Use the default key path unless the user requests a custom path. Recommend a passphrase, but allow the user to choose.

## Step 3: Start SSH Agent And Add The Key

Check the agent and loaded identities:

```bash
ssh-add -l
```

If the agent is not running, start it:

```bash
eval "$(ssh-agent -s)"
```

Add the selected private key:

```bash
ssh-add ~/.ssh/id_ed25519
```

Adjust the filename if a different key was selected. If the key has a passphrase, let the user enter it interactively.

## Step 4: Give The User The Public Key For GitHub

Show only the selected public key:

```bash
cat ~/.ssh/id_ed25519.pub
```

Then instruct the user:

1. Open GitHub in a browser.
2. Go to `Settings`.
3. Open `SSH and GPG keys`.
4. Choose `New SSH key`.
5. Use a recognizable title for this machine.
6. Paste the full public key output.
7. Save the key.

Pause until the user confirms the key was added.

## Step 5: Verify GitHub SSH Authentication

Run:

```bash
ssh -T git@github.com
```

Expected successful result:

```text
Hi <username>! You've successfully authenticated, but GitHub does not provide shell access.
```

If prompted about host authenticity, explain that `github.com` should be accepted only when the user intended to connect to GitHub, then let the user confirm.

From Cynthia11281128/my_agent, MIT.

More from Cynthia11281128/my_agent