ssh-jump-runcloud

Automates deployment of filesystem objects and execution of commands to remote hosts through a jump server, with optional cloud-based routing and encrypted payloads for hosts without direct SSH access.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/mattei2005/mgs-agent --skill ssh-jump-runcloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssh-jump-runcloud
Source: https://github.com/mattei2005/mgs-agent/tree/main/profiles/atena-skills/devops/ssh-jump-runcloud
Command: npx skills add https://github.com/mattei2005/mgs-agent --skill ssh-jump-runcloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of deploying files and running commands on RunCloud-hosted WordPress servers when direct SSH access is blocked, by using a ProxyJump-based SSH path or a no-SSH fallback through the WordPress Plugin Editor.

Core Features & Use Cases

  • ProxyJump SSH (S03 → S01) with expect: Copies files and executes commands on the target server (S01/RunCloud) using SSH jump through the reachable server (S03) while handling password prompts.
  • No-SSH fallback via WP Plugin Editor form POST: When SSH is fully blocked, deploys file content through the WordPress admin Plugin Editor using real admin credentials and a fresh nonce.
  • Persistence management (SOUL.md sync): Updates Atena’s durable rule identity by editing SOUL.md in the live Hermes profile and syncing the corresponding repository mirror, then committing and pushing with a 1Password-provided GitHub token.

Quick Start

Ask the skill to deploy your plugin or mu-plugin file to RunCloud server S01 by copying it from the mgs-agent machine to S01 through SSH ProxyJump (S03 → S01) and then verifying the deployed file and WordPress plugin/database state.

Frequently Asked Questions about ssh-jump-runcloud

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

FAQPage Schema
How do I deploy files to a RunCloud WordPress server when direct SSH is blocked?

Deploy files to RunCloud servers with blocked SSH by routing through an SSH ProxyJump host or falling back to the WordPress Plugin Editor form POST. The ProxyJump path copies files and runs commands via an intermediate reachable server.

How does SSH ProxyJump handle chained password prompts on RunCloud?

SSH ProxyJump handles chained password prompts on RunCloud using expect-based automation. This mechanism intercepts and responds to sequential authentication prompts when jumping from a reachable server to the target RunCloud server.

Can I use the WordPress Plugin Editor to deploy plugin code when SSH is unavailable?

Yes, you can use the WordPress Plugin Editor to deploy plugin code when SSH is unavailable. This fallback method uses a form POST with real admin credentials and a fresh nonce to inject file content directly.

Does deploying to RunCloud via ProxyJump require specific user permissions?

Yes, deploying to RunCloud via ProxyJump requires correct RunCloud user permissions to execute shell commands with sudo constraints. Validating WordPress filesystem and database outcomes ensures the deployment succeeded.

What is the best way to run remote shell commands on RunCloud without direct SSH access?

The best way to run remote shell commands on RunCloud without direct SSH access is routing through an SSH ProxyJump host using expect automation. This allows command execution and file copying while handling password prompts automatically.

Why does my WordPress Plugin Editor deployment fail on RunCloud?

WordPress Plugin Editor deployment on RunCloud fails if the nonce is stale or admin credentials are incorrect. This no-SSH fallback requires a fresh nonce and valid authentication to successfully POST file content.