Update to Adzviser Merchant Center

{
  "description": "Open an interactive Merchant Center report preview in ChatGPT so the user can inspect, edit, and run it. Use only for an explicit Preview UI, UI Mode, embedded report, or interactive report request. Do not use for raw rows, calculations, rankings, comparisons, audits, or ordinary analysis.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 250
    }
  ],
  "name": "adzviser-preview-ui-mode",
  "skill_md_contents": "---\nname: adzviser-preview-ui-mode\ndescription: Open an interactive Merchant Center report preview in ChatGPT so the user can inspect, edit, and run it. Use only for an explicit Preview UI, UI Mode, embedded report, or interactive report request. Do not use for raw rows, calculations, rankings, comparisons, audits, or ordinary analysis.\n---\n\n# Merchant Center Preview UI\n\nUse only for explicit interactive-preview requests. Use `adzviser-data-mode`\nwhen the answer requires actual reporting rows.\n\n1. Call `list_workspace` and choose the named workspace with Merchant Center\n   access. Ask when none is named and multiple suitable workspaces remain.\n2. Call `list_metrics_and_breakdowns_merchant_center` for exact fields.\n   Request only necessary fields. Keep product detail and issue reports\n   separate from performance analysis.\n3. Resolve inclusive dates using the current date and user's timezone. For\n   N days ending two days ago, use `[D-(N+1), D-2]`.\n4. Build `adzviser_request` with `workspace_name`, `date_ranges`, optional\n   `time_granularity`, and `assorted_requests.merchant_center_request`\n   containing `metrics` and optional `breakdowns`.\n5. Call `preview_and_retrieve_reporting_data` once. Let the user edit and run\n   it. A preview alone contains no final reporting rows; do not invent values\n   or claim to analyze hidden component data.\n\nCTR is a fractional ratio, displayed as a percentage after multiplying by 100.\nNumeric counts may be strings; preserve Product ID as text. Current product\ndetails and issues are not historical date-filtered performance. Repeated issue\nrows do not represent additional products. Customer country and target country\nare different fields. Keep currencies and reporting scopes separate.\n\nNever send `client_id`, `reporting_mode`, `_widget_action`, conversation history\nor unrelated context. Never call `set_reporting_mode` from the conversation.\nDate/Week/Month/Quarter belong in time_granularity, not breakdowns. Do not add\nunsupported filters or other sources.\n\nLet the component handle Run and mode controls. Analyze only model-visible rows.\nIf the user switches to analysis and rows are absent, use `retrieve_reporting_data`\nthrough Data Mode. Explain errors and missing access accurately. This plugin\ncannot edit or delete products, fix disapprovals, or change ad bids and budgets.\n"
}