peer-commands

Execute shell commands on registered peers through a daemon.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yanivprusman/automateLinux --skill peer-commands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: peer-commands
Source: https://github.com/yanivprusman/automateLinux/tree/main/.agent/skills/peer-commands
Command: npx skills add https://github.com/yanivprusman/automateLinux --skill peer-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables centralized, safe remote command execution across multiple peers without using direct SSH, enabling automated workflows and easier fleet management.

Core Features & Use Cases

  • Execute shell commands on registered peers through the daemon to coordinate updates and configuration changes.
  • Manage peer registrations and view statuses from a central controller.
  • Use Case: You need to pull the latest code on all workers from a single leader and verify the daemon is healthy, without logging into each machine.

Quick Start

Use d registerWorker to enroll a new worker. Then run a sample command on a peer with d execOnPeer --peer vps --directory /opt/automateLinux --shellCmd 'git pull'

Frequently Asked Questions about peer-commands

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

FAQPage Schema
How do I run commands on remote machines without using SSH?

To run commands on remote machines without SSH, you can use a daemon-based approach where a central controller executes shell commands on registered peers. This replaces direct SSH connections to enable automated workflows and safer fleet management.

What is the best way to execute shell commands across multiple distributed workers?

Executing shell commands across distributed workers is best handled by registering each worker with a central daemon. You can then issue commands like git pull from a leader node to coordinate updates and verify daemon health without logging into each machine individually.

Do I need to install any software on all peers to enable remote command execution?

Yes, to enable remote command execution, the daemon and its CLI tools must be installed and accessible on all designated peers. This setup allows the central controller to manage peer registrations and view statuses across the fleet.

How do I register a new worker for remote fleet management?

To register a new worker for fleet management, you use the CLI to enroll the peer with the central daemon. Once registered, you can execute targeted shell commands on that specific worker from your controller.

Why use a daemon for remote command execution instead of direct SSH?

Using a daemon for remote command execution instead of direct SSH enhances security and auditability. It provides a centralized method to coordinate configuration changes and updates across distributed IT environments without exposing direct shell access.