hand-off-a-task
Skill0 starsChanged 4 days agoMITView on GitHub
Hand a task to a Rush cloud agent and bring back the result. Use when someone wants work done off their machine or in the background (write tests, upgrade a dependency, research and write a report, investigate an incident), or asks what happened to a task Rush ran earlier.
In this repository5 other files it gives its agents.
- fix-a-bugSkill
- get-startedSkill
- review-a-prSkill
- run-in-parallelSkill
- save-an-agentSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Start it: Call create_session once, with a fresh UUID you write yourself as request_id (no shell command needed).
- Very specific: line 51
Work started earlier: When the person asks about Rush work without an id, call list_sessions (newest first.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hand off a task to Rush
Rush runs the task in its own cloud computer and keeps going while this
conversation moves on. Tool names may carry a client prefix
(mcp__rush__create_session). Never ask for a password, token or API key in
chat, and never report a result Rush did not return.
- Write the task. The session knows nothing from this conversation. Put in
taskthe goal, the files, errors, links and decisions that matter, and what done looks like: "open a pull request", "write the report as report.md", "answer in a few sentences". For code, add "do not merge" unless the person asked for a merge; the agent may otherwise follow merge rules of its own. To build on a finished session, pass its id ascontinue_from; its answer goes at the top of the new task. - Pick where it runs. For code, pass
repo: a GitHub repository, branch (/tree/<branch>) or pull request URL fromlist_repositories, or a gitlab.com project. If the team keeps a Project for that repository (list_projects), passprojectinstead; it brings the Project's standing instructions and secrets. Name a saved agent withagentwhen one fits (list_agents), and the accounts the task may use inconnections(list_connections). Leave out what the task does not need; with noagent, Claude Code does the work. - Start it. Call
create_sessiononce, with a fresh UUID you write yourself asrequest_id(no shell command needed). If the call errors and you retry, send the samerequest_idso only one session starts. For independent tasks, start one session each. - Wait. Tell the person it is running, then call
wait_for_sessionswith every id andtimeout_seconds: 50, again untilsettledis true. A session past the runs-at-once limit startsqueued; keep waiting. With several,until: "any"lets you report each one as it lands. - Read the result.
get_sessionhas the answer, branch, pull request and the files it made.get_session_changeslists the changed files (include_difffor the diff);get_session_artifactreads one file by name. Uselist_session_eventsonly to explain how the agent got there or why it failed. - Continue or stop.
send_session_messagecontinues in the same computer, with its files and conversation, for 7 days after it goes idle; follow it withwait_for_sessions.cancel_sessionstops the session and releases its computer, after which no follow-up is possible; ask before stopping one.
Report each session in a few lines: its status, the answer, and the pull
request or file links. needs_review means Rush could not confirm the result:
say so and show what the agent reported. On failed, give the error and the
next step; do not retry silently.
Work started earlier. When the person asks about Rush work without an id,
call list_sessions (newest first; filter by status), match on the first line
of each answer, then read the one they mean with get_session.
When Rush refuses
A refused call's text starts with a code, and often a Next: step; follow it.
For these, tell the person the fix in one line:
| Code | Fix |
TOKEN_LIMIT_REACHED, CREDITS_EXHAUSTED, SPEND_CAP_REACHED, PAYMENT_METHOD_REQUIRED, COMPUTE_LIMIT_REACHED, WEEKLY_COMPUTE_LIMIT_REACHED | Relay the message; it names the fix. Model accounts are at https://cloud.getrush.ai/console/settings/?section=accounts and billing at https://cloud.getrush.ai/console/settings/?section=billing |
RESOURCE_NOT_ACCESSIBLE | Rush's GitHub App does not reach that repository. Add it at https://cloud.getrush.ai/console/settings/?section=connections, or run without repo. |
CONNECTION_NOT_READY | Call connect_account with type app (gmail, linear, slack, …) or mcp (with its url), and name; for an agent made from a template, also agent. A gitlab.com project needs name gitlab. Give the authorize_url to the person to open in their own browser; never open or fetch it. It works once, for 10 minutes. Start the session again once list_connections shows it connected. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

