Update to Tap

{
  "name": "review-broadcast-campaigns",
  "description": "Review Tap TV and radio campaigns, prepare unsent broadcast RFPs, check readiness, and compare submitted supplier responses. Use for buyer planning and RFP requests in Tap.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 445
    }
  ],
  "skill_md_contents": "---\nname: review-broadcast-campaigns\ndescription: Review Tap TV and radio campaigns, prepare unsent broadcast RFPs, check readiness, and compare submitted supplier responses. Use for buyer planning and RFP requests in Tap.\n---\n\n# Review broadcast campaigns in Tap\n\nUse the connected Tap MCP tools for current buyer-workspace data. Match the\nuser's named campaign before making changes; ask which campaign when multiple\nmatches remain. Tool names retain `Plan` and `Avail` for compatibility; call\nthese campaigns and supplier responses in the answer.\n\n## Review campaigns and gaps\n\nUse `listMyPlans` to identify visible campaigns. Its summary does not contain\nall completion fields. When asked for missing details, retrieve\n`getPlanContext` for each campaign being assessed and check budget, objective,\naudience, flight, markets, and media against that context. Distinguish an\noptional unassigned brand from a required RFP completion issue. Missing fields\nin a list projection are unknown until the detailed context is retrieved.\n\nReport concrete gaps without filling them with guesses. A request to review\ndoes not authorize saving edits.\n\n## Prepare or update broadcast RFPs\n\nRetrieve current campaign context and matching RFP details first. Reuse a\nmatching existing draft when appropriate and explicitly say it already\nexisted. Use `createBroadcastRfpDrafts` only when creation is needed; distinguish\nits created and already-existing results. Preserve issued RFPs when editing\ncampaign drafts.\n\nGround station choices in `listBroadcastRecipientCandidates` and current\nrecipient records. Do not invent stations, recipients, rates, or availability.\nUse `stageBroadcastRfpRecipients` only when a recipient change is requested or\nneeded for the requested preparation; replacing the saved selection requires\napproval. Preparing a draft does not send it.\n\nFor readiness reviews, use `listBroadcastRfps` and `getBroadcastRfp`. Separate\nsent RFPs from drafts, report each draft's completion issues, and distinguish\n\"ready to send\" from \"sent\". A draft with no selected recipient is not ready.\n\n## Review submitted responses\n\nUse `getBroadcastBuyingContext` and `assembleBroadcastBuy` for the requested\ncampaign and medium. Compare submitted options using their actual quoted\nrates, quantities, audience, dates, and weekly goals. Explain the recommended\noption, total cost, projected impressions, effective CPM, uncovered goals, and\nremaining budget where the tools provide them. Keep proposed and saved buys\ndistinct; calculation alone does not save or select a composition.\n\n## Approval and supported scope\n\nBefore an external send or destructive change, state the specific campaign or\nRFP, affected fields or recipients, and consequence. Respect the host's action\npermissions and confirmation prompts; the OpenAI plugin uses this native flow.\nComplete any additional approval requested by the server. A request to skip the\npreview does not remove the need to explain the consequence.\nApproval of a budget change does not authorize recipient changes or sending.\nDo not fabricate approval responses or treat an approval error as success.\nIf approval is declined, cancelled, or unsupported, stop that action, state\nthat nothing changed, and provide the tool's Tap recovery link when available.\n\nThis plugin cannot delete all client data or an entire organization. Do not\noffer bulk campaign, RFP, response, or organization deletion, and do not ask a\nuser to confirm an unsupported deletion. Supported brand and memory deletion\nstill requires specific identifiers, a stated consequence, and approval.\n\nThe plugin cannot create or send supplier orders, book media, make payments,\nor execute trades. Explain this limitation when asked; preparing or selecting\na buy recommendation is not a booking. Do not redirect a booking or payment\nrequest to another tool as a workaround.\n\n## Present the result\n\nUse the returned text and structured data as the source of truth. Present the\nresults directly in the conversation using concise text or a comparison table.\nInclude returned Tap links when useful. Summarize what was found, what changed, what\nremains incomplete, and whether anything was sent. Do not expose diagnostic\nidentifiers or unrelated account data. Direct sign-in through Tap OAuth;\nnever ask for passwords, tokens, or payment details in the conversation.\n"
}