daily-check

Daily Check

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

Run a daily health check on all marketing accounts using the strategy context.

Modes

Pick the mode before step 0 — it decides how much you gather and how you report:

• Incremental (default) — the cheap daily run. Gather compact findings analytics-first (step 4), load the action_log as a subset (step 0), and report only what changed since the previous reports.daily summary (step 10's diff-first contract). This is what keeps context small and the report short.
• Deep — the full run: every step below at full depth (raw per-platform pulls, the full action_log, the full Healthy / Watch / Action-needed report). Use it when the user says "deep" or "full", on the first-ever run, or when the previous reports.daily summary is missing or older than 7 days (compare its generated_at / period against server_now's date). Recommend running a deep check once a week so the incremental diffs never drift from ground truth.

Mixed operation

Manual operation in the platform UI and mureo-driven operation coexist — most accounts run that way for a while after onboarding, and it applies to every platform. Treat any change you find that mureo did not make as a first-class fact, not an anomaly: the action_log records what mureo did, never the full history of the account, so never infer current state from it. When a diff surfaces a change made outside mureo, say so in the report rather than silently absorbing it into the new state.

Step 2b imports what mureo can fetch, so much of that work is now in action_log as origin: "external" before you start diagnosing. Two rules follow. First, an entry with origin: "external" is something mureo OBSERVED — never describe it as something mureo did, and never offer to roll it back (mureo refuses; it never saw the prior value). Second, and more important, import covers only the platforms with a change feed: for every platform step 2b reports unavailable or error, you are still working blind, and a quiet report from such a platform is not evidence that it was quiet. Say which platforms those were.