onboardlisted

# Onboard > PREREQUISITE: Read `../_mureo-shared/SKILL.md` for auth, security rules, output format, and **Tool Selection** (Read/Write on Code, `mureo_strategy_*` / `mureo_state_*` MCP on Desktop / Cowork). Guide me through setting up mureo for a new marketing account. ## Steps 1. **Check installation**: Verify mureo is installed by running `mureo --help`. If not found, guide the user to run `pip install mureo`. 2. **Check data mode (BYOD first, then auth)**: **Always run `mureo byod status` first.** If any platform shows `BYOD (N rows, ...)`, that platform is in **BYOD mode** — do NOT prompt the user to run `mureo auth setup` for it, do NOT call `mureo auth status` to "verify" it (that command reads `credentials.json` directly and ignores BYOD), and do NOT report it as "未認証". For BYOD platforms, announce: "Using BYOD CSV data (N rows, <date range>)." For the **remaining** platforms (those showing `not configured` or `real API`), then run `mureo auth status` to see which have OAuth credentials. If a platform is `not configured` for BYOD AND has no credentials, offer `mureo auth setup` (interactive — user runs it themselves) **or** offer the BYOD path: "Export a CSV from <platform> and run `mureo byod import <file>` instead." Never claim a platform is unauthenticated when `mureo byod status` shows it in BYOD mode. BYOD takes priority over OAuth and is sufficient on its own for analysis. Note: When calling MCP tools, you