From mureo
Generates a weekly marketing operations report covering goal progress, platform performance (Google Ads, Meta Ads, GA4), and action impact across platforms.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mureo:weekly-reportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> 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).
PREREQUISITE: Read
../_mureo-shared/SKILL.mdfor auth, security rules, output format, and Tool Selection (Read/Write on Code,mureo_strategy_*/mureo_state_*MCP on Desktop / Cowork).
Generate a weekly marketing operations report.
onboard skill first)Load context: Read STRATEGY.md and STATE.json.
Discover platforms: Identify all configured platforms and available data sources.
Period: Determine the reporting period (last 7 days from today).
Goal progress: For each Goal, pull performance data from the relevant platforms:
google_ads_performance_report (with period: "LAST_7_DAYS" then period: "LAST_14_DAYS" and subtract the first 7 from the next 7 for previous-week comparison). 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 performance-report tool over the same two windows and perform the WoW subtraction the same way.meta_ads_insights_report similarly. When summing Meta "results" across campaigns, group by result_indicator — never aggregate link_click totals together with pixel_lead totals (PR #61). If mureo's Meta Ads tools are unavailable, fall back to the official meta-ads-official hosted MCP for the raw insights over the same two windows; the official MCP does not surface a result_indicator field, so you must inspect each campaign's optimization goal / actions list yourself and avoid aggregating link_click-optimized totals with offsite_conversion.fb_pixel_lead-optimized totals — note this caveat in the report.byod/ directory (or ~/.mureo/byod/ for legacy CLI users) and is only accessible through mureo MCP tools — do not look for raw CSVs in the project directory.Actions taken: Read action_log from STATE.json, filter to the reporting period.
Present as a timeline:
| Date | Command | Action | Platform | Summary |
|---|
Impact assessment: For each action taken, evaluate impact using the relevant platform's trend/analysis tools. Cross-reference with GA4 data if available to validate on-site impact.
Cross-platform insights:
Next week recommendations:
/rescue, /budget-rebalance, /creative-refresh, /goal-review)Evidence pipeline: Include an evidence assessment section:
observation_due dates that passed this week — evaluate their outcomes by comparing metrics_at_action with current metricsPresent report in a structured format suitable for sharing with stakeholders:
Log to action_log in STATE.json that a weekly report was generated, including the reporting period.
Persist the report summary (best-effort): Call mureo_state_report_set with report="weekly" and a concise summary object so the read-only dashboard can render this report without re-running you. Follow this convention:
generated_at: ISO 8601 timestamp of this runperiod: the reporting window (e.g. "LAST_7_DAYS" or an explicit date range)kpis: per-platform and/or totals headline numbers (spend, conversions, cpa, week-over-week change)flags: a list of notable items (e.g. ["meta_ads_cpa_up_15pct"])narrative: the 2-3 sentence executive summaryThis is best-effort: if mureo_state_report_set is unavailable (e.g. a pure file-mode host without the context MCP), skip it silently — the rest of this skill still works.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub logly/mureo --plugin mureo