daemon-peer-execution

Execute commands on remote peers via the daemon peer networking infrastructure.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables running commands on remote peers through the daemon's peer networking infrastructure, replacing SSH-based remote execution with a unified, daemon-native approach.

Core Features & Use Cases

  • Peer-targeted execution: Run commands on any registered peer without SSH access, supporting distributed development and maintenance tasks.
  • Operator-friendly workflows: Centralized logging, status checks, and consistent error handling across peers.
  • Use Case: Deploy a Git pull to multiple peers to synchronize codebases during a coordinated release.

Quick Start

From your local machine, execute a command on a peer: d execOnPeer --peer vps --directory /opt/automateLinux --shellCmd "git status"

Frequently Asked Questions about daemon-peer-execution

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

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

To run commands on remote peers without SSH, use a daemon-native peer networking infrastructure. This approach replaces traditional SSH access with a unified daemon protocol, executing commands directly across a WireGuard-based peer network.

What is daemon-based remote execution over a WireGuard network?

Daemon-based remote execution is a method for issuing terminal commands across a peer network. It uses a TCP-based exec protocol on port 3600 with execRequest messages, capturing output via a subprocess on registered peers connected through WireGuard.

Do I need a leader registry to execute commands on remote peers?

Yes, you need a leader registry to execute commands on remote peers. The remote execution infrastructure requires daemons running on target peers, a leader registry to track them, and a TCP-based exec protocol on port 3600 to process the requests.

How do I deploy a Git pull to multiple peers simultaneously?

To deploy a Git pull to multiple peers, execute a command on the target peer using the daemon's execOnPeer function. You specify the peer name, target directory, and the shell command, such as git status, to synchronize codebases during a coordinated release.

SSH vs daemon peer networking for remote execution?

Daemon peer networking replaces SSH for remote execution by providing a unified, daemon-native approach. It leverages a WireGuard-based peer network and a centralized TCP protocol on port 3600, offering consistent logging and status checks without managing SSH access.