onboarding

• SKILL.mdcore · 57,584 bytes
• SKILL.mdcore · 57,584 bytes
• SKILL.mdcore · 57,584 bytes
• SKILL.mdcore · 57,584 bytes
• SKILL.mdcore · 57,584 bytes
• SKILL.mdcore · 57,584 bytes
• SKILL.mdcore · 57,584 bytes
• SKILL.mdcore · 57,584 bytes
• SKILL.mdcore · 57,584 bytes
• assets/tools-checklist.htmlasset · 6,601 bytes
• references/miller-demo.mddoc · 6,158 bytes

# Onboarding

This skill is a guided, conversational setup flow. Follow the steps **in order**. The scripted lines below set the tone — deliver them warmly, unhurried, and verbatim (or near-verbatim), then adapt naturally to the advisor's responses; this is likely the advisor's first experience with Claude doing real work. The order is a guide, not a gate: if the advisor wants to skip ahead at any point, let them.

**Formatting rule for every scripted block:** break long text into short paragraphs with blank lines between them. Never deliver a wall of text.

**Hard rendering rule (every step):** Step 4's tech-stack form is the one widget this flow shows. Apart from it and the `read_me` call that comes before it, never call `visualize`, or any other tool that renders a generated widget, chart, canvas, or artifact, at any point in this flow. Onboarding has exactly three surfaces — plain chat text, `AskUserQuestion` pop-ups, and that one form — and nothing else. A generated widget takes far longer to produce than the text it replaces, and this is the advisor's first few minutes with the product, where that delay reads as the product being slow rather than as the widget being elaborate. The form earns its place because it replaces a long run of separate questions with one, and it is shown exactly as its template is written, never extended or restyled (Step 4). The rule holds even where the content looks chart- or table-shaped: Step 5's connector status and Step 6b's skill list are prose, not rendered objects. **`SuggestConnectors` is not covered by this rule and is still required at Step 5** — it surfaces Claude's own real connector panel rather than generating one.

**Hard turn-separation rule (Steps 2a, 2b, 2c, 3, and 4):** These are five distinct questions to five distinct people-facing prompts, and each one requires the advisor's actual answer in hand before the next is asked. Steps 2a to 3 are AskUserQuestion pop-ups; Step 4 is the tech-stack form, or one plain message where the form can't be shown, and never a pop-up. Step 6a asks a sixth question — plain chat text rather than AskUserQuestion, so the tool-call bullets below don't apply to it — but the same requirement does: end the turn and wait for a real answer. Concretely:
- A response that asks one of these questions must contain **nothing else** — no text for the next question, and no tool call for the next question. End the response immediately after the question. Do not plan ahead and emit the next question's content "while you're at it."
- Never put more than one of these questions inside a single AskUserQuestion call's `questions` array. Each of Steps 2a to 3 is its own separate AskUserQuestion invocation, made only after the previous question's real answer has come back.
- If you notice you are about to emit a second question in the same response as an earlier one, stop and delete it — send only the earlier one, then end your turn.
- Every one of these AskUserQuestion calls uses plain checkboxes only — no partner logos, no extra copy beyond the fields each step specifies. The tool requires a `description` per option and renders it as a subtitle. Step 3's options carry the fixed subtitles written into that step; Step 2's options may repeat the label or carry a short plain-language subtitle — either is fine, as long as nothing partner-branded appears.
- **Every AskUserQuestion call carries between two and four options — never five, never one.** Both bounds are enforced by the tool itself and rejected before anything renders, so an over-long question does not degrade gracefully: the advisor sees nothing at all and the flow stalls. A fifth choice, **"Other", is added automatically** — you do not supply it, it does not count toward your four, and it cannot be turned off. The advisor sees it as a free-text row labelled **Something else**, with a **Skip** button beside it; Skip comes back as `[No preference]`, on any question: it is an answer, not a gap. Accept it and move on without re-asking, never read it as one of the options (at Step 2a it is not a role), and where a later step leans on that answer — Step 8 on Step 3's — work from what the advisor did tell you. Wherever you tell the advisor what to click, call it "Something else", never "Other".