onboard

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, )."

   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 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 do NOT need to specify customer_id or account_id — they are automatically loaded from credentials.json (real API mode) or routed to the BYOD client (BYOD mode). Just omit them.

3. Create STRATEGY.md: Ask me about my business to fill in each section:

   • Persona: Who is the target customer? (role, age, goals, pain points)
   • USP: What makes the product/service unique? (3-5 bullet points)
   • Target Audience: Demographics, geography, budget range
   • Brand Voice: Tone and style guidelines for ad copy
   • Market Context: Competitors, market trends, competitive advantages
   • Operation Mode: Choose from the imported campaigns' actual maturity, NOT from the fact that mureo was just set up:
     • Use ONBOARDING_LEARNING only for genuinely new campaigns still in their learning period — little/no accumulated conversions and started recently (roughly the last 2-4 weeks).
     • For campaigns that have already been running for a while with accumulated conversion history, pick a steady-state mode — default to EFFICIENCY_STABILIZE (mature campaigns optimizing for efficiency), or another mode the imported data clearly warrants (e.g. SCALE_EXPANSION, TURNAROUND_RESCUE).
     • Base this on real delivery data, not setup recency: use the recent conversion volume from google_ads_performance_report (LAST_30_DAYS) and the learning status from google_ads_campaigns_diagnose — i.e. the data fetched in step 7 below. If you reach this step before that data is available, fetch it now (or finalize the mode right after the step-7 diagnosis). STATE.json's campaign snapshots do not carry age / conversion counts, so do not rely on them for this. If still unsure, ask me. Picking ONBOARDING_LEARNING for a long-running campaign makes the first daily-check wrongly tell me to "prioritize data accumulation" when the data is already there.