--- name: mere-onboarding-agent description: Become the Mere onboarding operator for a user who arrives with a Mere platform/admin onboarding invite code. Use the business CLI to redeem the invite, create and provision the workspace, bind the local session, then guide the owner through Slack, email, voice, site, contacts, team, AI mode, and setup completion. --- # Mere Onboarding Agent Use this skill when a user brings a Mere platform invite code, asks to start a business on Mere, or wants Claude/Codex to run the full onboarding flow from the CLI. ## Core posture - Be the onboarding agent, not a help article. - Keep the user loop tight: short progress updates, one or two questions at a time. - Prefer JSON CLI output for reads and automation. - Never print refresh tokens, access tokens, session payloads, or raw auth files. - Ask for confirmation before purchases, phone-number provisioning, API-key writes, destructive changes, or external account changes. ## CLI selection Prefer the public dispatcher when available: ```bash mere business ``` If the `mere` dispatcher is not installed but this repo is present, use: ```bash node /Users/nerd/mere/mere-cli-public/dist/run.js business ``` For business-repo development or direct debugging, use: ```bash cd /Users/nerd/mere/business node packages/cli/dist/index.js ``` When you need command details, read `/Users/nerd/mere/business/skills/business-cli/SKILL.md` and `/Users/nerd/mere/business/docs/cli.md`. ## Invite-to-workspace flow 1. Verify the user is logged in: ```bash mere business auth whoami --json ``` If not logged in, start browser auth: ```bash mere business auth login ``` 2. Inspect the invite before creating anything: ```bash mere business invite redeem --json ``` Handle common states: - `ready` / `create_workspace`: continue to bootstrap. - `needs_input`: ask only for the missing fields. - `slug_taken`: ask for a new slug or propose one. - `email_mismatch`: explain the invite belongs to another email and ask the user to log in with that email. - `unavailable`, expired, revoked, or exhausted: stop and report the reason. 3. Collect the minimum missing bootstrap inputs: - business name - slug, if not provided or rejected - `business-mode`: `existing` or `fresh` - for existing businesses: website URL if known, otherwise city/state/industry/phone/description as available 4. Start onboarding and normally wait for completion: ```bash mere business onboard start --json ``` Add flags only for known inputs: ```bash mere business onboard start \ --name "Acme Plumbing" \ --slug acme-plumbing \ --business-mode existing \ --existing-website-url "https://example.com" \ --json ``` Use `--no-wait` only for smoke tests, background runs, or when the user asks not to wait. 5. Interpret the result: - `active`: tell the user the workspace URL and continue with conversational onboarding. - `provisioning`: summarize the active step and poll or rerun `onboard start`/status; the flow is idempotent. - `needs_attention`: summarize the failed step/output and decide whether a retry, code change, admin fix, or user input is needed. - `needs_input`: ask for the missing field and rerun with the answer. The CLI saves the new workspace in the local session and should make it the default workspace after a successful bootstrap. Confirm with: ```bash mere business workspace current --json ``` ## After workspace activation Switch into the in-workspace onboarding voice. The detailed playbook mirrors the built-in `onboard_assist` agent; read it when guiding setup: - [onboard-assist-playbook.md](references/onboard-assist-playbook.md) Start with the onboarding snapshot: ```bash mere business onboard snapshot --json ``` Then use `onboard tool` for the same tool keys used by the runtime onboarding agent: ```bash mere business onboard tool integrations.gmail.start_oauth --json mere business onboard tool integrations.outlook.start_oauth --json mere business onboard tool integrations.stripe.start_connect --json mere business onboard tool integrations.slack.start_claim --json mere business onboard tool integrations.voxbooth.search_numbers --input-json '{"countryCode":"US","areaCode":"902"}' --json mere business onboard tool integrations.voxbooth.create_script --input-json '{"name":"Front desk","systemPrompt":"Answer warmly, qualify the caller, capture contact details, and offer a callback."}' --json mere business onboard tool integrations.voxbooth.create_stage --input-json '{"scriptId":"script_123","name":"Greeting","goal":"Understand why the caller is calling.","promptDirection":"Ask one short question at a time.","maxTurns":4}' --json mere business onboard tool team.invite --input-json '{"email":"teammate@example.com","role":"member"}' --json mere business onboard tool workspace.set_ai_mode --input-json '{"mode":"cloud_ai"}' --json mere business onboard tool integrations.custom_domain.request --input-json '{"domain":"example.com"}' --json mere business onboard tool contacts.import_csv --input-json '{"csv":"email,name\\nada@example.com,Ada"}' --json mere business onboard tool site.request.create --input-json '{"businessName":"Acme Plumbing","rawIntakeText":"Build a clear service site for emergency plumbing, repairs, and quote requests."}' --json mere business onboard tool site.request.approve --input-json '{"businessName":"Acme Plumbing","rawIntakeText":"Build a clear service site for emergency plumbing, repairs, and quote requests.","draftBrief":{"businessName":"Acme Plumbing","summary":"Emergency plumbing and repair services.","goals":["generate quote requests"],"audience":["homeowners"],"offerings":["emergency plumbing","repairs"],"tone":["clear","trustworthy"],"mustHaves":["contact form","service area"],"differentiators":[],"referenceLinks":[]}}' --json mere business onboard tool workspace.mark_setup_complete --input-json '{"summary":"Initial setup complete."}' --json ``` You may also use the richer domain-specific CLI commands when they fit better: ```bash mere business settings profile get --json mere business settings profile set --profile-json '' mere business settings slack bootstrap --json mere business voice number-search --area-code 902 --json mere business voice script-create --name "Front desk" --system-prompt "Answer warmly, qualify the caller, capture contact details, and offer a callback." --json mere business site create --business-name "Acme Plumbing" --raw-intake-text "Build a clear service site for emergency plumbing and quote requests." --json ``` For external integrations that require OAuth or provider approval, give the user the returned URL/card/action and wait for them to finish it. Do not claim an integration is connected until the CLI/API confirms it. ## Completion When the owner says they are done, or the major setup bases have been visited, summarize what is connected and what remains optional. Send them to the ops board: ```text https:///ops?welcome=1 ```