[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78P4BWMP4MC7Z0Q5RP43PKC":3,"skill-same:01M78P4BWMP4MC7Z0Q5RP43PKC":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M78P4BWMP4MC7Z0Q5RP43PKC","hand-off-a-task",null,"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.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fphnx-labs\u002Frush-mcp\u002Fskills\u002Fhand-off-a-task\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hand-off-a-task\ndescription: 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.\n---\n\n# Hand off a task to Rush\n\nRush runs the task in its own cloud computer and keeps going while this\nconversation moves on. Tool names may carry a client prefix\n(`mcp__rush__create_session`). Never ask for a password, token or API key in\nchat, and never report a result Rush did not return.\n\n1. **Write the task.** The session knows nothing from this conversation. Put in\n   `task` the goal, the files, errors, links and decisions that matter, and\n   what done looks like: \"open a pull request\", \"write the report as\n   report.md\", \"answer in a few sentences\". For code, add \"do not merge\" unless\n   the person asked for a merge; the agent may otherwise follow merge rules of\n   its own. To build on a finished session,\n   pass its id as `continue_from`; its answer goes at the top of the new task.\n2. **Pick where it runs.** For code, pass `repo`: a GitHub repository, branch\n   (`\u002Ftree\u002F\u003Cbranch>`) or pull request URL from `list_repositories`, or a\n   gitlab.com project. If the team keeps a Project for that repository\n   (`list_projects`), pass `project` instead; it brings the Project's standing\n   instructions and secrets. Name a saved agent with `agent` when one fits\n   (`list_agents`), and the accounts the task may use in `connections`\n   (`list_connections`). Leave out what the task does not need; with no\n   `agent`, Claude Code does the work.\n3. **Start it.** Call `create_session` once, with a fresh UUID you write\n   yourself as `request_id` (no shell command needed). If the call errors and\n   you retry, send the same `request_id` so only one session starts. For\n   independent tasks, start one session each.\n4. **Wait.** Tell the person it is running, then call `wait_for_sessions` with\n   every id and `timeout_seconds: 50`, again until `settled` is true. A session\n   past the runs-at-once limit starts `queued`; keep waiting. With several,\n   `until: \"any\"` lets you report each one as it lands.\n5. **Read the result.** `get_session` has the answer, branch, pull request and\n   the files it made. `get_session_changes` lists the changed files\n   (`include_diff` for the diff); `get_session_artifact` reads one file by\n   name. Use `list_session_events` only to explain how the agent got there or\n   why it failed.\n6. **Continue or stop.** `send_session_message` continues in the same computer,\n   with its files and conversation, for 7 days after it goes idle; follow it\n   with `wait_for_sessions`. `cancel_session` stops the session and releases\n   its computer, after which no follow-up is possible; ask before stopping one.\n\nReport each session in a few lines: its status, the answer, and the pull\nrequest or file links. `needs_review` means Rush could not confirm the result:\nsay so and show what the agent reported. On `failed`, give the error and the\nnext step; do not retry silently.\n\n**Work started earlier.** When the person asks about Rush work without an id,\ncall `list_sessions` (newest first; filter by `status`), match on the first line\nof each answer, then read the one they mean with `get_session`.\n\n## When Rush refuses\n\nA refused call's text starts with a code, and often a `Next:` step; follow it.\nFor these, tell the person the fix in one line:\n\n| Code | Fix |\n|---|---|\n| `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:\u002F\u002Fcloud.getrush.ai\u002Fconsole\u002Fsettings\u002F?section=accounts and billing at https:\u002F\u002Fcloud.getrush.ai\u002Fconsole\u002Fsettings\u002F?section=billing |\n| `RESOURCE_NOT_ACCESSIBLE` | Rush's GitHub App does not reach that repository. Add it at https:\u002F\u002Fcloud.getrush.ai\u002Fconsole\u002Fsettings\u002F?section=connections, or run without `repo`. |\n| `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. |\n","# Hand off a task to Rush\n\nRush runs the task in its own cloud computer and keeps going while this\nconversation moves on. Tool names may carry a client prefix\n(`mcp__rush__create_session`). Never ask for a password, token or API key in\nchat, and never report a result Rush did not return.\n\n1. **Write the task.** The session knows nothing from this conversation. Put in\n   `task` the goal, the files, errors, links and decisions that matter, and\n   what done looks like: \"open a pull request\", \"write the report as\n   report.md\", \"answer in a few sentences\". For code, add \"do not merge\" unless\n   the person asked for a merge; the agent may otherwise follow merge rules of\n   its own. To build on a finished session,\n   pass its id as `continue_from`; its answer goes at the top of the new task.\n2. **Pick where it runs.** For code, pass `repo`: a GitHub repository, branch\n   (`\u002Ftree\u002F\u003Cbranch>`) or pull request URL from `list_repositories`, or a\n   gitlab.com project. If the team keeps a Project for that repository\n   (`list_projects`), pass `project` instead; it brings the Project's standing\n   instructions and secrets. Name a saved agent with `agent` when one fits\n   (`list_agents`), and the accounts the task may use in `connections`\n   (`list_connections`). Leave out what the task does not need; with no\n   `agent`, Claude Code does the work.\n3. **Start it.** Call `create_session` once, with a fresh UUID you write\n   yourself as `request_id` (no shell command needed). If the call errors and\n   you retry, send the same `request_id` so only one session starts. For\n   independent tasks, start one session each.\n4. **Wait.** Tell the person it is running, then call `wait_for_sessions` with\n   every id and `timeout_seconds: 50`, again until `settled` is true. A session\n   past the runs-at-once limit starts `queued`; keep waiting. With several,\n   `until: \"any\"` lets you report each one as it lands.\n5. **Read the result.** `get_session` has the answer, branch, pull request and\n   the files it made. `get_session_changes` lists the changed files\n   (`include_diff` for the diff); `get_session_artifact` reads one file by\n   name. Use `list_session_events` only to explain how the agent got there or\n   why it failed.\n6. **Continue or stop.** `send_session_message` continues in the same computer,\n   with its files and conversation, for 7 days after it goes idle; follow it\n   with `wait_for_sessions`. `cancel_session` stops the session and releases\n   its computer, after which no follow-up is possible; ask before stopping one.\n\nReport each session in a few lines: its status, the answer, and the pull\nrequest or file links. `needs_review` means Rush could not confirm the result:\nsay so and show what the agent reported. On `failed`, give the error and the\nnext step; do not retry silently.\n\n**Work started earlier.** When the person asks about Rush work without an id,\ncall `list_sessions` (newest first; filter by `status`), match on the first line\nof each answer, then read the one they mean with `get_session`.\n\n## When Rush refuses\n\nA refused call's text starts with a code, and often a `Next:` step; follow it.\nFor these, tell the person the fix in one line:\n\n| Code | Fix |\n|---|---|\n| `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:\u002F\u002Fcloud.getrush.ai\u002Fconsole\u002Fsettings\u002F?section=accounts and billing at https:\u002F\u002Fcloud.getrush.ai\u002Fconsole\u002Fsettings\u002F?section=billing |\n| `RESOURCE_NOT_ACCESSIBLE` | Rush's GitHub App does not reach that repository. Add it at https:\u002F\u002Fcloud.getrush.ai\u002Fconsole\u002Fsettings\u002F?section=connections, or run without `repo`. |\n| `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. |\n",{"name":5,"description":7},"main","2a6d24be2ed571c5ff2319c506b60741bbcb1cb0","plugins\u002Fphnx-labs\u002Frush-mcp\u002Fskills\u002Fhand-off-a-task",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hand-off-a-task",{"tool":40,"command":41},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hand-off-a-task",{"tool":43,"command":44},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hand-off-a-task","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fphnx-labs\u002Frush-mcp\u002Fskills\u002Fhand-off-a-task\u002FSKILL.md",true,[],[49,58,66,74,82,90],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]