Update to Adszy

{
  "name": "performance-brief",
  "description": "Create an evidence-backed Google Ads performance brief through Adszy MCP. Use for week-over-week, month-over-month, or year-over-year comparisons, stakeholder updates, client reports, and concise performance recaps.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 218
    }
  ],
  "skill_md_contents": "---\nname: performance-brief\ndescription: Create an evidence-backed Google Ads performance brief through Adszy MCP. Use for week-over-week, month-over-month, or year-over-year comparisons, stakeholder updates, client reports, and concise performance recaps.\n---\n\n# Performance Brief\n\nTurn Adszy's read-only metrics into a concise stakeholder-ready narrative.\n\n## Workflow\n\n1. Resolve the account with `list_ad_accounts` when it is ambiguous.\n2. Call `compare_periods` with the user's requested comparison.\n3. Call `get_account_summary` for the current-period campaign breakdown.\n4. Use a focused diagnostic tool only when the comparison needs support, such as `get_change_history`, `get_budget_pacing`, or `get_anomalies`.\n5. Write:\n   - executive summary;\n   - key metric changes;\n   - campaign drivers;\n   - risks or unknowns;\n   - recommended next checks.\n\n## Guardrails\n\n- State both date ranges and the account currency.\n- Use absolute and percentage changes where available.\n- Do not invent explanations for movements. Separate measured drivers from hypotheses.\n- Flag low volume, missing conversion data, and attribution limitations.\n- Do not imply that Adszy applied any recommendation.\n- Keep the brief readable without hiding material negative findings.\n"
}