What problem does it solve? Agents running on different machines (laptop, DevBox, Azure VM) cannot easily hand off work without manual file copying and terminal pasting. This Skill defines a git-based task queuing pattern so agents on one machine can assign, execute, and collect results from another machine automatically. ## Core Features & Use Cases - Git-Based Task Queuing: Tasks are defined as YAML files in .squad/cross-machine/tasks/ and results written to .squad/cross-machine/results/, synchronized through git push/pull cycles. - GitHub Issues Fallback: Urgent or ad-hoc tasks can be submitted as GitHub Issues with squad:machine-{name} labels for the target machine's agent to pick up. - Security Validation Pipeline: Tasks pass schema validation, command whitelisting, resource limits (timeout, memory, CPU), and execution isolation before running. - Use Case: A laptop agent needs GPU voice cloning done on a DevBox. It writes a task YAML file, commits and pushes it; the DevBox agent polls the queue, validates and executes the command, then commits the result file back for the laptop to read. ## Quick Start Create a YAML task file in .squad/cross-machine/tasks/ with the target machine and command, then commit and push it so the remote agent picks it up on its next cycle.
