Update to Appy Coupons - deals+discounts

{
  "description": "Prepare a coupon-expiry reminder when the user asks to be reminded before an offer ends. Show the relevant offer with the `coupons` app tool, resolve an exact reminder time and timezone, and guide the optional widget or host scheduled-task flow. Never claim a button was clicked or a reminder exists without host-visible confirmation.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 225
    }
  ],
  "name": "coupon-expiry-reminder-setup",
  "skill_md_contents": "---\nname: coupon-expiry-reminder-setup\ndescription: Prepare a coupon-expiry reminder when the user asks to be reminded before an offer ends. Show the relevant offer with the `coupons` app tool, resolve an exact reminder time and timezone, and guide the optional widget or host scheduled-task flow. Never claim a button was clicked or a reminder exists without host-visible confirmation.\n---\n\n# Coupon expiry reminder setup\n\nPrepare a precise, one-time reminder handoff for a coupon with a stated expiry.\n\n## Inputs\n\nResolve the target coupon, its explicit expiry date, the desired lead time or reminder date and time, and the user's timezone. Ask when any of these details are ambiguous or when multiple coupons could be the target.\n\n## Workflow\n\n1. Identify the coupon from user-supplied data or model-visible `coupons` structured content. Do not rely on private widget state, including the expanded row.\n2. Require an explicit, unambiguous expiry. If the expiry is missing or uncertain, ask the user for it rather than creating a speculative reminder.\n3. Resolve an exact future reminder date, local time, and timezone that fall before the stated expiry. For a date-only expiry, do not invent an expiry hour; schedule on an earlier date at a user-approved time.\n4. Call `coupons` with the relevant offer before the task handoff. Preserve its facts and append the stated expiry and reminder target to `notes`. Do not call the tool with an empty list.\n5. Tell the user to use the widget's task or reminder action if one is visible. The action is runtime-configured and may be absent. Do not say that you selected it.\n6. Provide a copy-ready fallback prompt containing the coupon name, code when present, source URL when present, exact reminder timestamp and timezone, stated expiry, and important restrictions. The user can submit it through a host that supports scheduled tasks.\n7. Confirm creation only after the host returns explicit confirmation. Otherwise describe the reminder as prepared, not scheduled, and tell the user where confirmation should appear.\n\n## Boundaries\n\n- The `coupons` MCP tool cannot create, inspect, update, or verify scheduled tasks.\n- This skill cannot see or click widget-only controls.\n- Scheduled-task availability depends on the host, workspace settings, and runtime widget configuration.\n- Do not promise that a reminder will run, and do not turn a one-time expiry reminder into recurring coupon monitoring without a separate user request.\n\n## Output\n\nReturn the relevant coupon widget, the resolved reminder details, and either task-action guidance or a copy-ready scheduling prompt.\n"
}