← ClaudeAtlas

sync-statelisted

Sync STATE.json with current campaign data from all platforms. Use when the user asks to refresh state, sync campaigns, update STATE.json from live data, or pull latest campaign snapshots.
logly/mureo · ★ 9 · AI & Automation · score 75
Install: claude install-skill logly/mureo
# Sync State > 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). Synchronize STATE.json with the current state of all marketing platforms. ## Prerequisites - STRATEGY.md and STATE.json should exist in the current directory (run the `onboard` skill first if not) ## Steps 1. **Read current STATE.json** (if exists) to track changes. 2. **Discover platforms**: Identify all platforms registered in STATE.json `platforms`. 3. **Fetch platform data**: For each registered platform: - **Google Ads**: prefer mureo native — call `google_ads_campaigns_list`, then `google_ads_performance_report` for the current period (last 30 days). Both work in BYOD and Live API modes. If mureo's Google Ads tools are unavailable (e.g. `MUREO_DISABLE_GOOGLE_ADS=1` after `mureo providers add google-ads-official`), fall back to the official `google-ads-official` MCP's equivalent campaign-list and performance-report tools for the same period. - **Meta Ads**: prefer mureo native — call `meta_ads_campaigns_list`, then `meta_ads_insights_report` for the current period — capture `result_indicator` per campaign so STATE.json reflects whether each campaign's "results" are clicks or real leads. If mureo's Meta Ads tools are unavailable, fall back to the official `meta-ads-official` hosted MCP for the campaign list and insights; the `result_indicator` field is