relaylisted

Use claude-relay to run a long or rate-limit-prone task autonomously across subscription accounts. Invoke this skill whenever the user says "use relay", "run this with relay", "do this overnight", "run this autonomously", "use relay for X", or has a multi-hour / multi-step task they want to hand off completely. Also use proactively when a task looks like it will take many turns and the user hasn't thought about rate limits yet. Guides goal writing, picks the right flags, and starts the run.
oleg-koval/agent-skills · ★ 3 · AI & Automation · score 75

Install: claude install-skill oleg-koval/agent-skills

# relay Runs a task **unattended** using `claude-relay`: drives `claude -p` in a headless loop, writes a handoff summary when one account's limit approaches, and switches to the next account automatically. You watch logs; relay handles the rest. Binary: `claude-relay` (alias `relay` if added to shell). Config: `~/.claude-relay/relay.config.json`. --- ## Step 1: Decide: relay or inline? **Use relay when:** - Task will take many turns or hours (big refactor, migration, research + implementation) - The user wants to hand it off and walk away - Rate limits are a real concern (long-running or token-heavy) **Stay inline when:** - Task is quick (< ~10 turns) - User wants to review each step - Task needs interactive input that relay can't provide --- ## Step 2: Write the goal A relay goal is a self-contained spec a fresh Claude agent can execute cold. Write it to `/tmp/relay-goal-<short-name>.md`. It must include: - **What to do**: concrete deliverables, not vague intent - **How to verify**: the exact command proving success (`npm test`, `curl /api/health`, etc.) - **Scope**: explicit list of what NOT to do (no commits, no PRs, no migrations, unless stated) - **Key files**: paths the agent should read first if the context isn't obvious **Template:** ```markdown ## Goal <1-3 sentences: the deliverable> ## Success criteria Run `<command>` and confirm it exits 0 / returns the expected result. ## Scope -