get-started
First run with Rush. Use right after the plugin is installed, or when someone asks what Rush is, how to start, or how to hand it their first task.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- get-started
- description
- First run with Rush. Use right after the plugin is installed, or when someone asks what Rush is, how to start, or how to hand it their first task.
03 SKILL.md 正文
Get started with Rush
Take the person from install to one finished task in three short turns. Never ask for a password, token or API key in chat, and never invent a result.
- Check the connection and ask. Call
list_repositories. If the client asks the person to sign in, tell them to finish signing in to Rush (in Claude Code:/mcp, then Rush) and stop until they have. Then say in one sentence what Rush is: an agent that does a task in its own cloud computer and hands back the result with a record of what it did. Ask one question: "What would you like done? It can be on one of your repositories, or need none." If the list is empty, add that a task on code needs the Rush GitHub App on that repository (https://cloud.getrush.ai/console/settings/?section=connections), or, for a gitlab.com project, a GitLab sign-in (connect_accountwithtypeappandnamegitlab). - Start it. Confirm the repository against the list when the task names
one. Then follow the
hand-off-a-taskskill: write the task with everything the agent needs, start it, say it takes a few minutes, and wait until it settles. - Report and close. Give the answer, the pull request link if there is one, and any files it made. Then say how to continue: ask for the next task in plain words, reply to this one to keep going in the same computer for 7 days, and see every run at https://cloud.getrush.ai.
Runs use the Claude or ChatGPT account the person connected to Rush; without
one, Rush's models cover a first try. If the start is refused, use the table in
hand-off-a-task under "When Rush refuses".
04 同仓库更多 Skills
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.
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.
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.
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.
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.
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.