fleet-ssh

Execute shell commands over SSH on multiple fleet machines simultaneously.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/phyter1/seed --skill fleet-ssh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet-ssh
Source: https://github.com/phyter1/seed/tree/main/.claude/skills/fleet-ssh
Command: npx skills add https://github.com/phyter1/seed --skill fleet-ssh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables running arbitrary shell commands across multiple fleet machines through SSH, facilitating remote management tasks that are not covered by the seed CLI.

Core Features & Use Cases

  • Remote Command Execution: Send and run commands on specific fleet machines or all machines simultaneously.
  • Operational Diagnostics: Perform checks like process listings, logs review, or service management remotely.
  • Use Case: Imagine needing to check the system uptime on all fleet machines quickly. Use this Skill to execute uptime across ren1, ren2, and ren3 in parallel with a single command.

Quick Start

Use the fleet-ssh skill to run 'ps aux' on ren2 to check running processes.

Frequently Asked Questions about fleet-ssh

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

FAQPage Schema
How do I run shell commands on multiple fleet machines via SSH simultaneously?

To run shell commands on multiple fleet machines via SSH, you provide a command and target machine names like ren1 or ren2. The Skill executes them in parallel using your default SSH setup, returning results for quick remote diagnostics and management.

Can I use this for remote diagnostics like checking uptime or process listings across distributed machines?

Yes, you can perform remote diagnostics like checking uptime or process listings across distributed machines. It sends and runs ad-hoc shell commands such as `ps aux` or `uptime` on specific fleet machines, returning the output for operational review.

Do I need to configure a separate SSH protocol setup to execute ad-hoc commands on a fleet?

No, you do not need a separate SSH protocol setup to execute ad-hoc commands on a fleet. The Skill depends on Bash scripting and uses your user's default SSH configuration, requiring no additional dependencies or environment setup to run commands remotely.

What is the best way to manage services remotely on a distributed fleet using Bash scripting?

The best way to manage services remotely using Bash scripting is by executing commands across all or specific fleet machines simultaneously. This Skill applies to system administrators needing secure, automated service management and operational diagnostics without interacting with each machine individually.

Are there limitations when executing remote commands across fleet machines with Bash scripts?

A limitation of executing remote commands with Bash scripts is that it relies entirely on your default SSH setup and does not cover management tasks included in the seed CLI. It is designed for quick ad-hoc command execution rather than complex stateful orchestration.