prod-ssh

Enables credentialed SSH access to a host with operator-approved multi-factor authentication.

43|2|Updated Jan 25, 2024
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill prod-ssh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prod-ssh
Source: https://github.com/glowingkitty/OpenMates/tree/main/.agents/skills/prod-ssh
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill prod-ssh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prod SSH requires human-gated 3FA (SSH key + password + TOTP), which prevents Claude from running production commands unattended; this Skill coordinates the secure handshake and makes it possible to execute needed tasks after approval.

Core Features & Use Cases

  • Temporary prod-side access window: Guides the user to open and later close an expiring SSH window on the production server using the provided start script.
  • Operator-provided TOTP handshake: Prompts for a 6-digit TOTP and uses it to open a master SSH connection, then avoids further prompts for subsequent commands.
  • Controlled command execution: Enables running operational commands needed for production investigation (e.g., Docker/service status, logs, filesystem inspection) via the dedicated command wrapper.
  • Decision support to avoid SSH: Encourages using cheaper alternatives (OpenObserve logs/traces/debug tooling or Vercel debug helpers) when SSH is unnecessary.
  • Safety and failure diagnosis: Includes explicit failure-mode guidance for common issues like missing prereqs, closed access windows, fail2ban lockouts, and misconfigured environment variables.

Quick Start

Tell the user to open the temporary SSH window on prod using the start script with your dev public key and wait for confirmation before you proceed.

Frequently Asked Questions about prod-ssh

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

FAQPage Schema
How do I use AI to SSH into a production server with 3FA enabled?

To use AI to SSH into a production server with 3FA, you need a workflow that coordinates the human-gated 3FA handshake by prompting for a 6-digit TOTP to open a master SSH connection for command execution.

What is the best way to run production diagnostics without exposing secrets in chat?

The best way to run production diagnostics safely is by using a dedicated command wrapper that executes operational commands over a master SSH connection, ensuring you can inspect server state without exposing secrets in chat.

How do I set up a temporary SSH access window for production operations?

You set up a temporary SSH access window by running a provided start script on the production server with your public key, opening an expiring connection that must be manually closed after operations complete.

Do I need to provide a TOTP every time I run a production command via SSH?

You do not need to provide a TOTP for every command; providing a fresh 6-digit TOTP during the initial master SSH connection handshake opens the session for subsequent command execution without further prompts.

Why does automated SSH to prod fail with a fail2ban lockout or closed access window?

Automated SSH to prod fails when prerequisites are missing, the temporary access window is closed, or fail2ban lockouts occur, requiring explicit failure-mode diagnosis and handling to re-establish the connection.

When should I avoid SSH for production server diagnostics?

You should avoid SSH for production server diagnostics when cheaper alternatives like OpenObserve logs, traces, or debug tooling are sufficient, reserving SSH access for when non-SSH debug alternatives cannot solve the issue.