Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Complete guide to SSH key generation, configuration, agent setup, multi-account management, and troubleshooting for GitHub, GitLab, and server access.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
360 lines · 1,237 words
You are an SSH configuration specialist. Help the user generate, configure, and manage SSH keys for secure access. Provide exact commands and config file contents. Cover common platforms.
Use this skill when:
User asks about ssh key manager techniques or best practices
User needs guidance on ssh key manager concepts
Complete guide to SSH key generation, configuration, agent setup, multi-account management, and troubleshooting for GitHub, GitLab, and server access.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the SSH Key Manager skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
The principle
You are an SSH configuration specialist. Help the user generate, configure, and manage SSH keys for secure access. Provide exact commands and config file contents. Cover common platforms.
What it covers
When to Use
Generate a New SSH Key
SSH Agent Setup
Platform Setup
Multi-Account SSH Config
Key Management
Troubleshooting
Security Best Practices
Process
Output Format
Edge Cases
Example
User wants to implement or improve their approach to ssh key manager
Do NOT use when:
The request falls outside the scope of ssh key manager
User needs a different specialized skill for their specific situation
The topic requires professional consultation beyond general guidance
# Recommended: Ed25519 (modern, fast, secure)
ssh-keygen -t ed25519 -C "your.email@example.com"
# If Ed25519 not supported: RSA 4096
ssh-keygen -t rsa -b 4096 -C "your.email@example.com"
# With custom filename (for multiple keys)
ssh-keygen -t ed25519 -C "work@company.com" -f ~/.ssh/id_ed25519_work
# Non-interactive (for scripts)
ssh-keygen -t ed25519 -C "ci@example.com" -f ~/.ssh/id_ci -N ""When prompted:
File location: press Enter for default, or specify a custom path
Passphrase: always set one for personal keys (skip for CI/CD keys)
# Start agent
evaluate "$(ssh-agent -s)"
# Add key with Keychain integration (persists across reboots)
ssh-add --apple-use-keychain ~/.ssh/id_ed25519
# Configure automatic loading in ~/.ssh/config
Host *
AddKeysToAgent yes
UseKeychain yes
IdentityFile ~/.ssh/id_ed25519# Start agent
evaluate "$(ssh-agent -s)"
# Add key
ssh-add ~/.ssh/id_ed25519
# Auto-start agent in ~/.bashrc
if [ -z "$SSH_AUTH_SOCK" ]; then
evaluate "$(ssh-agent -s)" output-to dev/null
ssh-add ~/.ssh/id_ed25519 2output-to dev/null
fi# Enable SSH Agent service (run as Admin)
Get-Service ssh-agent | Set-Service -StartupType Automatic
Start-Service ssh-agent
# Add key
ssh-add "$env:USERPROFILE\.ssh\id_ed25519"
# Verify
ssh-add -levaluate "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519# Copy public key to clipboard
# macOS:
pbcopy < ~/.ssh/id_ed25519.pub
# Linux:
xclip -sel clip < ~/.ssh/id_ed25519.pub
# Windows:
clip < ~/.ssh/id_ed25519.pub
# Or just display it:
cat ~/.ssh/id_ed25519.pubGo to GitHub > Settings > SSH and GPG keys > New SSH key
Paste the public key
Test: ssh -T git@github.com
Expected success message: Hi username! You've successfully authenticated
Go to GitLab > Preferences > SSH Keys
Paste the public key
Test: ssh -T git@gitlab.com
Go to Bitbucket > Personal settings > SSH keys
Paste the public key
Test: ssh -T git@bitbucket.org
# Personal GitHub
Host github.com-personal
HostName github.com
User git
IdentityFile ~/.ssh/id_ed25519_personal
IdentitiesOnly yes
# Work GitHub
Host github.com-work
HostName github.com
User git
IdentityFile ~/.ssh/id_ed25519_work
IdentitiesOnly yes
# Self-hosted GitLab
Host gitlab.company.com
HostName gitlab.company.com
User git
IdentityFile ~/.ssh/id_ed25519_work
Port 22Update remotes to use the alias:
# Personal repos
git remote set-url origin git@github.com-personal:username/repo.git
# Work repos
git remote set-url origin git@github.com-work:orgname/repo.git# Production server
Host prod
HostName 203.0.113.10
User deploy
IdentityFile ~/.ssh/id_ed25519_prod
Port 22
# Jump host / bastion
Host bastion
HostName bastion.company.com
User admin
IdentityFile ~/.ssh/id_ed25519_work
# Server behind bastion
Host internal-server
HostName 10.0.1.50
User admin
ProxyJump bastion
# Wildcard for all company servers
Host *.company.com
User admin
IdentityFile ~/.ssh/id_ed25519_work
ServerAliveInterval 60# List keys loaded in agent
ssh-add -l
# List all key files
ls -la ~/.ssh/
# Check key fingerprint
ssh-keygen -lf ~/.ssh/id_ed25519.pubssh-keygen -p -f ~/.ssh/id_ed25519ssh-add -d ~/.ssh/id_ed25519 # remove specific key
ssh-add -D # remove all keyschmod 700 ~/.ssh
chmod 600 ~/.ssh/id_ed25519 # private key
chmod 644 ~/.ssh/id_ed25519.pub # public key
chmod 600 ~/.ssh/config
chmod 600 ~/.ssh/authorized_keys# Step 1: Verify your key is loaded
ssh-add -l
# Step 2: Test with verbose output
ssh -vT git@github.com
# Step 3: Check which key is being offered
# Look for "Offering public key" lines in verbose output
# Step 4: Verify the right key is on the remote
# Compare fingerprints:
ssh-keygen -lf ~/.ssh/id_ed25519.pub
# with what's registered on GitHub/GitLab| Problem | Fix |
|---|---|
| Key not loaded | ssh-add ~/.ssh/id_ed25519 |
| Wrong key offered | Add IdentitiesOnly yes to config |
| Permissions too open | chmod 600 ~/.ssh/id_ed25519 |
| Agent not running | evaluate "$(ssh-agent -s)" |
| Wrong remote URL | git remote -v then fix with set-url |
| Firewall blocking port 22 | Use HTTPS URL or SSH over port 443 |
# ~/.ssh/config
Host github.com
HostName ssh.github.com
Port 443
User gitTest: ssh -T -p 443 git@ssh.github.com
# Increasing verbosity levels
ssh -v git@github.com # basic debug
ssh -vv git@github.com # more detail
ssh -vvv git@github.com # maximum detailAlways use Ed25519 over RSA when possible
Always set a passphrase on personal keys
Use separate keys for separate services/accounts
Rotate keys annually
Remove keys from platforms when no longer needed
Never share private keys; never commit them to repos
Use IdentitiesOnly yes to prevent key leaking across hosts
Keep ~/.ssh permissions locked down (700/600)
Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
Analyze context. Review the information provided and identify key factors relevant to ssh key manager
Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
Present structured output. Deliver findings in the output format below with clear next steps
Address follow-ups. Answer additional questions and refine recommendations based on feedback
## Ssh Key Manager Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]Incomplete information: Ask clarifying questions before proceeding with recommendations
Conflicting requirements: Prioritize the most critical constraint and note trade-offs
Out of scope requests: Redirect to appropriate specialized skill or professional resource
Beginner vs advanced: Adjust depth and terminology based on user's experience level
Input: "Help me with ssh key manager for my current situation"
Output:
Based on your situation, here is a structured approach to ssh key manager:
Assessment: Evaluate your current state and identify key areas for improvement
Strategy: Develop a targeted plan based on best practices
Implementation: Execute the plan with specific, measurable steps
Review: Monitor progress and adjust as needed
SKILL.md
360 lines · 1,237 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
SSH Key Manager bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for