remote-exec

Execute remote commands over SSH for git sync, file transfer, and tmux jobs.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/Khamel83/oneshot --skill remote-exec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remote-exec
Source: https://github.com/Khamel83/oneshot/tree/main/archive/v9/skills/remote-exec
Command: npx skills add https://github.com/Khamel83/oneshot --skill remote-exec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates remote command execution across a brain/body architecture via SSH, enabling git sync, file transfer, and long-running jobs from a single control plane.

Core Features & Use Cases

  • Unified remote execution: Run commands across multiple machines via SSH with consistent context and output.
  • Git sync and deployment workflows: Coordinate pushes/pulls and remote updates in structured steps.
  • Data transfer and long-running tasks: Transfer files between machines, start long-running jobs in tmux, and monitor progress from a central location.

Quick Start

Ask it to run a command on a target machine, such as 'uptime' on homelab.

Frequently Asked Questions about remote-exec

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

FAQPage Schema
How do I execute remote commands on multiple machines via SSH from a single control plane?

You can execute remote commands across multiple machines via SSH by using a defined machine registry to coordinate git sync, file transfers, and long-running jobs from a central location. This provides consistent context and unified output for each operation.

What is the best way to manage long-running jobs on remote machines using tmux?

Managing long-running jobs in tmux involves starting the tasks on remote machines over SSH. This approach allows you to monitor progress and manage the persistent sessions centrally without losing execution state if the connection drops.

How do I transfer files between remote hosts using rsync over SSH?

Transferring files between remote hosts with rsync requires SSH access to the configured machines. By orchestrating the transfer through a central control plane, you can securely move data and coordinate updates between the systems.

Do I need a machine registry to automate git sync workflows across remote machines?

Yes, a defined machine registry is required to automate git sync workflows across remote machines. It provides the necessary SSH access targets and configuration needed to coordinate pushes, pulls, and remote updates reliably.

Can I run git deployment workflows on a homelab server using SSH?

Yes, you can run git deployment workflows on a homelab server using SSH. By targeting the specified machine in your registry, you can execute structured steps for pushes, pulls, and remote updates from your central control plane.

What are the limitations of coordinating remote execution across a brain and body architecture?

The primary limitation of coordinating remote execution is its strict dependency on standard CLI tools like git, rsync, and tmux. Reliable operation requires proper SSH access and a correctly defined machine registry to function without errors.