← ClaudeAtlas

setuplisted

Walk the user through rote's first run: import the MCP servers they already use, compile one of their skills, and show that the compiled skill gives the same answer, faster and cheaper. Use when the user says "set up rote", "get started with rote", "try rote on my skills", "onboard me", or just installed rote and asks what to do first.
trevhud/rote · ★ 8 · AI & Automation · score 71
Install: claude install-skill trevhud/rote
# Set up rote You relay `rote setup`. rote asks the questions and makes the plans, and the user answers them. You never answer a question or approve a plan yourself, and you never pass `--yes`. ## 1. Run it ```sh uvx --from rote-cli rote setup --agent-mode yes --json ``` It prints one JSON object on stdout. Exit 0 or 1 with `status: "done"` means it finished: go to step 3. ## 2. Each stop: ask, then run `next` Exit 2 is a stop with `status: "action_required"`. Tell the user what `ask` says, in your own plain words, with the step it belongs to (`step.index` of `step.total`). Keep money and time in it when the plan spends any. Then wait for their answer. | `reason` | What the user decides | What you run | | --- | --- | --- | | `missing_answer` | the question in `ask`, from `choices` (`skills` and `servers` describe them) | `next[0].command`, with the placeholder replaced by their answer as `answer_with` says | | `confirmation_required` | yes or no to the plan | yes: `next[0].command`, no: `next[1].command` | | `authorization_pending` | approve each `logins[].authorization_url` in their browser | once they say done: each `rote mcp login --complete` command in `next`, then the last `next` command | | `person_required` | run `next[0].command` in their own terminal (you cannot) | once they say done: the last `next` command | Run exactly the command `next` gives. rote remembers earlier answers, so it carries only the new one. Never add a flag it does not name. An error (exit