{"id":78409,"plugin_id":"plugin_asdk_app_6ad7518d3a808191aa5b92ab27901ba2","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T12:13:45.606Z","digest":"bc6c256624a0cc009f488560f75bd9417f2cc2df2307022f250886bffbf6b615","against":null,"payload":{"description":"Builds a weekly multi-platform advertising report through the Pilot MCP server: consolidated spend and results across Google Ads and Meta Ads, week-over-week changes, budget pacing and the traffic seen in Google Analytics 4. Use when the user asks for a weekly report, a weekly recap or last week's performance. Triggers: weekly report, weekly recap, how did last week go. Déclencheurs : rapport hebdomadaire, bilan de la semaine, récap hebdo, point de la semaine dernière.","included_files":[],"name":"weekly-performance-report","skill_md_contents":"---\nname: weekly-performance-report\ndescription: \"Builds a weekly multi-platform advertising report through the Pilot MCP server: consolidated spend and results across Google Ads and Meta Ads, week-over-week changes, budget pacing and the traffic seen in Google Analytics 4. Use when the user asks for a weekly report, a weekly recap or last week's performance. Triggers: weekly report, weekly recap, how did last week go. Déclencheurs : rapport hebdomadaire, bilan de la semaine, récap hebdo, point de la semaine dernière.\"\ncompatibility: \"Requires the Pilot MCP server (https://app.pilot.braike.com/mcp) connected in the client and authorized on a workspace with at least one ad platform attached.\"\nmetadata:\n  pilot-mcp-server: \"https://app.pilot.braike.com/mcp\"\n  pilot-mcp-tools: \"pilot_data_freshness pilot_cross_platform_overview pilot_budget_pacing google_list_accounts google_get_campaign_performance meta_list_accounts meta_get_account_performance_summary meta_compare_periods_performance google_analytics_run_report\"\n  pilot-mcp-read-only: \"true\"\n---\n\n# Weekly performance report\n\nProduce a one-page weekly report across the ad platforms of the workspace: what was spent, what it brought, what changed against the previous week, and what to watch. Answer in the user's language.\n\n## Requirements\n\n- **Required MCP server:** Pilot MCP (`https://app.pilot.braike.com/mcp`), authorized on the workspace to report on.\n- **Optional MCP servers:** a file storage server to save the report, a team messaging server to post it to a channel, a note-taking server to archive it. None is needed to build the report.\n- **Read-only:** never call a tool that creates, updates, pauses or deletes anything, on Pilot or on any other server.\n\n## Tools\n\n- `pilot_data_freshness`: whether the collected data covers the week.\n- `pilot_cross_platform_overview`: spend and results consolidated across platforms, ratios computed on totals.\n- `pilot_budget_pacing`: campaigns capped by their budget, and budgets left idle.\n- `google_list_accounts`: the Google Ads accounts attached to the workspace.\n- `google_get_campaign_performance`: Google Ads campaigns over the week.\n- `meta_list_accounts`: the Meta ad accounts attached to the workspace.\n- `meta_get_account_performance_summary`: Meta account KPIs over the week.\n- `meta_compare_periods_performance`: Meta results this week against the previous week.\n- `google_analytics_run_report`: sessions and key events by channel in Google Analytics 4.\n\n## Steps\n\n1. Call `pilot_data_freshness`. If a platform is stale, say so at the top and treat its figures as partial.\n2. Call `pilot_cross_platform_overview` with `days: 7`, then with `days: 14`; derive the previous week as the difference. If the tool refuses a money total because currencies differ, report each currency separately.\n3. Google Ads: call `google_list_accounts`, then `google_get_campaign_performance` with `date_range: \"LAST_7_DAYS\"` for each attached account. Keep the five campaigns with the most spend and the largest changes.\n4. Meta Ads: call `meta_list_accounts`, then `meta_get_account_performance_summary` with `date_preset: \"last_7d\"` and `meta_compare_periods_performance` with `period1: \"last_7d\"` and `period2: \"last_14d\"`. The second period contains the first: the previous week is the difference.\n5. Call `pilot_budget_pacing` with `days: 7` to flag capped and idle budgets.\n6. If a Google Analytics 4 property is attached, call `google_analytics_run_report` with `dateRanges` for the last 7 days and the 7 days before, `dimensions: [\"sessionDefaultChannelGroup\"]` and `metrics: [\"sessions\", \"keyEvents\"]`.\n7. Write the report.\n\n## Output\n\n1. **Headline**: total spend, total conversions or value, and the change against last week, in one sentence.\n2. **By platform**: a table with spend, conversions, cost per conversion and the week-over-week change.\n3. **What moved**: the three largest changes, with their likely cause when the data shows it.\n4. **Budget**: capped and idle budgets.\n5. **To watch next week**: two or three points.\n\n## Rules\n\n- State the dates covered and the currency of every amount.\n- Never add amounts in different currencies.\n- A ratio with an empty denominator is not available, not zero.\n- Skip a platform the workspace has not attached, without treating it as an error.\n\n## Examples\n\n- \"Give me the weekly report for this workspace.\"\n- \"Fais-moi le rapport hebdomadaire Google Ads et Meta, avec les variations.\"\n- \"How did last week go compared with the week before?\"\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}