Update to ChatGPT Ads Manager

{
  "description": "Help users understand and troubleshoot Ads Manager through read-only connector evidence, official Help Center guidance, and shared playbooks. Use for standalone campaign planning, reviews of supplied context hints, product-feed suitability, how-to and targeting-support questions, delivery issues, spend or performance questions, and conversion-reporting problems without changing Ads Manager state. Direct existing-account setup/readiness, billing setup, and logo requests belong to Account Admin.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 265
    },
    {
      "relative_path": "references/_shared/ads-structure-and-context-playbook.md",
      "size_in_bytes": 5598
    },
    {
      "relative_path": "references/_shared/auction-readiness-playbook.md",
      "size_in_bytes": 2059
    },
    {
      "relative_path": "references/_shared/event-quality.md",
      "size_in_bytes": 4060
    },
    {
      "relative_path": "references/_shared/help-center-guide.md",
      "size_in_bytes": 5455
    },
    {
      "relative_path": "references/_shared/measurement-readiness-playbook.md",
      "size_in_bytes": 2134
    },
    {
      "relative_path": "references/_shared/product-feed-contract.md",
      "size_in_bytes": 3578
    }
  ],
  "name": "ads-manager-help",
  "skill_md_contents": "---\nname: ads-manager-help\ndescription: Help users understand and troubleshoot Ads Manager through read-only connector evidence, official Help Center guidance, and shared playbooks. Use for standalone campaign planning, reviews of supplied context hints, product-feed suitability, how-to and targeting-support questions, delivery issues, spend or performance questions, and conversion-reporting problems without changing Ads Manager state. Direct existing-account setup/readiness, billing setup, and logo requests belong to Account Admin.\nallowed-tools:\n  - list_ad_accounts\n  - get_onboarding_status\n  - show_account_setup_widget\n  - get_identity_verification_status\n  - list_campaigns\n  - get_campaign\n  - list_ad_groups\n  - get_ad_group\n  - list_ads\n  - get_ad\n  - get_ad_account_insights\n  - get_campaign_insights\n  - get_ad_group_insights\n  - get_ad_insights\n  - get_conversion_insights\n---\n\n# Ads Manager Help\n\nUse this skill with the `ads_manager` app declared in `.app.json`. Its allowed tools resolve from the installed Ads Manager connector. Combine three sources without blurring them together:\n\n1. connector reads for the user's current account state;\n2. the [Ads Manager Help Center collection](https://help.openai.com/en/collections/20001223) and the topic map in [references/help-center-guide.md](references/_shared/help-center-guide.md) for official product guidance;\n3. careful interpretation for the likely cause and smallest safe next step.\n\nKeep the workflow read-only.\n\nBefore advancing into Help Center guidance or account-specific diagnosis, read and follow every reference whose branch condition matches the active workflow; when multiple conditions match, load all of them before proceeding. Every Help workflow requires [help-center-guide.md](references/_shared/help-center-guide.md).\n\nLoad playbooks only for the advice being requested:\n\n- For campaign/ad-group organization, drafting or reviewing supplied context hints, or ad/landing-page alignment, read [ads-structure-and-context-playbook.md](references/_shared/ads-structure-and-context-playbook.md).\n- For objective, budget-period, timing, or bidding-strategy decisions, read [auction-readiness-playbook.md](references/_shared/auction-readiness-playbook.md).\n- For conversion-measurement readiness or setup advice, read [measurement-readiness-playbook.md](references/_shared/measurement-readiness-playbook.md).\n- For Event Quality Score (EQS) explanations or enablement questions, read [event-quality.md](references/_shared/event-quality.md). Route account-specific scores to `$ads-manager-insights` and improvement recommendations to `$ads-manager-review`.\n- For product-feed suitability, product-set planning, or feed-ad launch quality, read the Planning Guidance section of [product-feed-contract.md](references/_shared/product-feed-contract.md#planning-guidance), including when no feed mode has been selected.\n\nThese references provide advice and do not expand this skill's allowed tools. Do not load unrelated playbooks for ordinary how-to questions or factual account reads.\n\n## Route The Request\n\n- For an existing account's remaining setup steps, billing setup, or logo setup, invoke `$ads-manager-account-admin`. Keep generic how-to questions here.\n- For standalone planning or a review of supplied hints, use the relevant playbook and the user's supplied facts. Do not require account selection or invoke a creation/editing skill to give advice. Open current Help Center guidance when the answer depends on product support, limits, setup, or other changing facts. If the user requests a create or update, hand off to the owning workflow.\n- For general how-to or product questions, read [references/help-center-guide.md](references/_shared/help-center-guide.md), open the matching Ads Manager Help Center article, and answer with its direct link. Inspect account data only for a relevant account-specific question when an available read can establish the needed fact.\n- For questions about supported countries, geographic levels, exclusions, radius targeting, or other targeting capabilities, use the matching current Help Center article rather than geo lookup probes or catalog enumeration. When the user needs concrete places resolved for campaign targeting, hand off to the applicable ad-creation or entity-management workflow and its geo guidance.\n- For account-specific troubleshooting, inspect the smallest relevant connector scope first, then use Help Center guidance to explain the observed state and remediation.\n- If connector tools are unavailable, provide general playbook and Help Center guidance grounded in supplied facts, and state that the user's current account state was not inspected when relevant.\n\n## Guardrails\n\nRead and follow the copied Guardrails in [references/help-center-guide.md](references/_shared/help-center-guide.md) before using Help Center guidance or connector evidence.\n\n## Account-Specific Workflow\n\n1. **Resolve scope.** Identify the ad account and affected campaign, ad group, or ad. Read a known identifier directly; otherwise use the narrowest list tool. Ask one concise question only when multiple plausible targets remain.\n2. **Inspect readiness when relevant.** Use onboarding status for setup symptoms or when no usable account is found. For an identity-verification state or progress question, resolve the account and call `get_identity_verification_status`; its connector-owned status and `recommended_next_step` are authoritative for whether identity action is required. If it reports `not_required`, explain that no identity action is needed. If it reports `completed`, `needs_review`, `submitted`, `pending`, `processing`, or `in_review`, advise waiting; do not tell the user to complete or resubmit verification. Do not infer billing, eligibility, approval, or verification from missing fields.\n\n   During delivery troubleshooting where account setup could explain the problem, call `get_onboarding_status` for the selected account. Show `show_account_setup_widget` once when available only if that successful read confirms `billing_setup_status=required` or `has_account_logo=false` with `logo_in_review=false` and no known logo submission awaiting review. Unknown billing, pending review, completed setup, or a failed or inconclusive read alone do not qualify. If status conflicts with a known submission, skip the widget. If the widget is unavailable or fails, state the confirmed setup state plainly.\n\n3. **Trace the hierarchy.** Read the affected resource and necessary parents. Request `serving_issues` or the equivalent live expansion when available. Preserve the resource level, status, issue code or label, and message.\n4. **Inspect performance.** Use bounded insight reads and state the date range and granularity. Check delivery indicators before conversions. Distinguish zero, null, delayed, partial, and unavailable data; zero conversions alone does not prove broken tracking.\n5. **Research guidance.** Use [references/help-center-guide.md](references/_shared/help-center-guide.md) to open the troubleshooting article and the most relevant topic-specific Ads Manager article. Search the collection for the observed issue only when the map has no good match. If no relevant article exists, say so and keep the recommendation explicitly evidence-based or provisional.\n6. **Prioritize.** Rank explicit blockers first, configuration mismatches second, and performance or measurement hypotheses last. Give the supporting evidence, confidence, and smallest safe remediation for each.\n\n## Response\n\nFor standalone planning or supplied-hint review, answer the requested question directly and follow the playbook's review format when applicable. Keep proposed advice separate from claims about current account state.\n\nFor general help, answer directly with official Help Center links and note any account-specific facts that would require connector inspection.\n\nFor troubleshooting, return:\n\n1. **Scope** — selected account and resources, plus the inspected time window.\n2. **Observed state** — connector facts and evidence gaps.\n3. **Help Center guidance** — documentation-derived guidance with direct links.\n4. **Prioritized diagnosis** — likely causes with confidence and evidence.\n5. **Remediation** — ordered user actions in Ads Manager and read-only checks that can confirm recovery.\n6. **Limits** — unresolved ambiguity or unsupported actions.\n\nKeep facts, interpretation, and documentation guidance visibly separate. Never expose secrets or dump raw connector responses when a concise evidence summary is enough.\n"
}