remote-agentslisted

# Remote Agents A long-running coding-agent task tied to the local session dies the moment the laptop sleeps, the network drops, or the session ends. This skill submits the job to a remote host as a detached process instead — it keeps running independent of the connection, and file-based state means checking on it later is just reading files, not maintaining a live session. ## When to use this - The task will run long enough that keeping a local session open for it is wasteful or risky (network drop, laptop sleep). - The work should survive you closing the laptop and checking back later. - The task should run on a different machine than the current one (more resources, a specific environment, isolation from local state). - **Not for short interactive work** — the setup overhead (self-contained prompt, submit/poll/collect cycle) isn't worth it for anything that finishes in a couple of minutes with you watching. ## Instructions ### 1. Write a fully self-contained prompt The remote job gets **zero context from this session** — only what's in the prompt you hand it. It must include: - The task itself, stated completely (no "as discussed above" — there is no above). - Verification commands the job should run to confirm its own work (see [`verify-before-done`](../verify-before-done) for what counts as real evidence). - Any constraints (files it must not touch, style/conventions to follow). - A **REPORT contract**: ask the job to print a clearly delimited block at t