Menu
Add an SSH public key to a remote server's authorized_keys file
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Save working documents to .context/ with proper frontmatter
Rebase a contributor's PR onto latest main. Fetches the PR, creates a backup branch on origin, sets up a worktree, analyzes divergence, rebases, and force-pushes back to the contributor's fork. Use when a PR needs to be brought up to date with main.
Merge source branch (default main) to production, create a CalVer release, and generate release content (GitHub release notes, Discord announcement, blog post)
Analyze branch commits, identify fixup candidates, rebase with autosquash, and post a PR comment explaining the cleanup.
Create a well-structured GitHub issue from a conversation or description
Link or unlink a local library for testing in a consumer project. Handles build, npm install from path, and cleanup. Default action is "link". Use "unlink" to reverse.
| name | add-ssh-key |
| description | Add an SSH public key to a remote server's authorized_keys file |
| argument-hint | <public-key> <user@host> |
| allowed-tools | ["Bash","Read"] |
Add an SSH public key to a remote server so a user can authenticate via SSH.
Parse $ARGUMENTS for:
ssh-rsa, ssh-ed25519, ecdsa-sha2-*, or sk-*user@host format (e.g., root@134.122.74.255)If either is missing, ask the user to provide it.
ssh-rsa, ssh-ed25519, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521, sk-ssh-ed25519@openssh.com, sk-ecdsa-sha2-nistp256@openssh.com)If invalid, show what was received and ask the user to double-check.
ssh -o ConnectTimeout=5 -o BatchMode=yes <user@host> "echo ok"
If this fails, inform the user they don't have access to the server and cannot proceed.
Before adding, check if the key already exists:
ssh <user@host> "grep -F '<base64-portion-of-key>' ~/.ssh/authorized_keys 2>/dev/null"
Extract the base64 portion (second field) for matching. If the key is already present, tell the user and stop — do not add it again.
Show the user a summary before making changes:
SSH KEY ADDITION
Server: <user@host>
Key: <key-type> <first 30 chars of base64>...<last 10 chars> <comment>
Comment: <comment from key>
Proceed? (yes / cancel)
After user confirms, append the key to the existing authorized_keys file:
ssh <user@host> "echo '<full-public-key>' >> ~/.ssh/authorized_keys"
Do NOT create directories or change permissions — assume ~/.ssh/authorized_keys already exists with correct permissions.
After adding, confirm the key is present:
ssh <user@host> "tail -1 ~/.ssh/authorized_keys"
Report success and remind the user to have the key owner test access:
Key added successfully. Ask them to test with: ssh <user@host>