ssh-setup-profile

Configure SSH host aliases in ~/.ssh/config with key-based authentication.

2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/NagyVikt/codex-plugins --skill ssh-setup-profile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssh-setup-profile
Source: https://github.com/NagyVikt/codex-plugins/tree/main/plugins/ssh-skill/skills/setup-profile
Command: npx skills add https://github.com/NagyVikt/codex-plugins --skill ssh-setup-profile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of manually managing SSH configurations and the security risks associated with storing credentials in insecure locations.

Core Features & Use Cases

  • Standardized Configuration: Automatically generates and updates ~/.ssh/config entries with best-practice security settings.
  • Credential Safety: Enforces SSH key-based authentication and prevents the storage of plaintext passwords.
  • Use Case: When you need to connect to multiple production and staging servers, this skill ensures each environment has a unique, secure alias that Codex can use for automated tasks.

Quick Start

Ask the assistant to set up a new SSH profile for your production server by providing the alias, host IP, username, and the path to your private key.

Frequently Asked Questions about ssh-setup-profile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure SSH host aliases for automated server access?

To configure SSH host aliases, this skill automatically generates and updates ~/.ssh/config entries with best-practice security settings. It enables secure, persistent server access for development, staging, and production infrastructure management.

What is the best way to manage SSH configurations for multiple staging and production servers?

The best way to manage SSH configurations for multiple servers is by using standardized alias generation. This skill creates unique, secure aliases for each environment, ensuring Codex can execute automated tasks without friction.

How do I set up an SSH profile with key-based authentication and a non-root user?

You set up an SSH profile by providing the alias, host IP, username, and private key path. The skill enforces strict security protocols, requiring key-based authentication and non-root user access to prevent insecure credential storage.

Can I use this SSH configuration approach for environment-specific DevOps automation?

Yes, you can use this approach for DevOps automation. It facilitates environment-specific connectivity by securely mapping host aliases in your local SSH config, allowing automated workflows to target specific infrastructure safely.

Why does my SSH config require key-based authentication instead of plaintext passwords?

Your SSH config requires key-based authentication to ensure credential safety. This skill prevents the storage of plaintext passwords and enforces strict security protocols to protect access to your infrastructure.

Are there limitations to managing SSH config files manually for server access?

Managing SSH config files manually introduces friction and security risks, such as storing credentials in insecure locations. This skill solves these issues by standardizing configuration generation and enforcing secure authentication protocols.