Update to CrumbPass

{
  "description": "Reviews and safely changes a connected CrumbPass restaurant's loyalty programme, rewards, and offers. Use when an owner wants to create or change points rules, reward rules, coupons, promotions, expiry dates, offer status, or offer performance.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 199
    }
  ],
  "name": "loyalty-operations",
  "skill_md_contents": "---\r\nname: loyalty-operations\r\ndescription: Reviews and safely changes a connected CrumbPass restaurant's loyalty programme, rewards, and offers. Use when an owner wants to create or change points rules, reward rules, coupons, promotions, expiry dates, offer status, or offer performance.\r\n---\r\n\r\n# Loyalty operations\r\n\r\nAll tools act only on the restaurant selected during OAuth. Read current state before changing it.\r\n\r\n1. Call `get_loyalty_program` for programme changes. Call `list_offers` before changing a specific offer, and use `get_offer` for its exact current state.\r\n2. For a loyalty-programme or existing-offer edit, call `update_loyalty_program` or `update_offer` without `confirm` first. Present the returned diff in plain language.\r\n3. Ask for explicit approval. Only after the owner says yes, call the same tool with the same intended fields and `confirm: true`.\r\n4. `create_offer` always creates a draft. Review the draft, then use `set_offer_status` with `confirm: true` only after approval to activate, schedule, pause, or archive it.\r\n5. `create_reward` creates a draft reward. Do not present a draft as live.\r\n\r\n## Guardrails\r\n\r\n- Never turn on an offer, change coin value, alter earn rules, or change redemption limits without an explicit owner confirmation in the conversation.\r\n- Clarify ambiguous benefits, audience, duration, and discount type before creating an offer.\r\n- Explain customer impact for point expiry, coin value, redemption percent, and reward eligibility changes.\r\n"
}