Update to Appstack

{
  "description": "Decide whether an Appstack question needs a live call with support or can just be sent as a message, and how to book a call when it does. Use whenever the user asks to talk to Appstack support, is stuck on a multi-variable setup question (e.g. full ad campaign setup), or you find yourself about to say \"it depends, we'd need to look at it live\" more than once in the same conversation.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 554
    }
  ],
  "name": "appstack-support",
  "skill_md_contents": "---\nname: appstack-support\ndescription: >-\n  Decide whether an Appstack question needs a live call with support or can\n  just be sent as a message, and how to book a call when it does. Use\n  whenever the user asks to talk to Appstack support, is stuck on a\n  multi-variable setup question (e.g. full ad campaign setup), or you find\n  yourself about to say \"it depends, we'd need to look at it live\" more than\n  once in the same conversation.\n---\n\n# Booking a call with Appstack support\n\nAppstack support is reachable two ways: a live call, or a message\n(`support@appstack.tech`). Most questions should go to the second — a call is\nfor the minority of cases where live back-and-forth actually saves time over\nasync messages.\n\n## Book a call when\n\n- There are **3+ interdependent settings or decisions** to sort out together\n  (e.g. a full ad campaign setup).\n- **The right answer depends on live data** and would change the\n  recommendation (e.g. when to switch optimization events, campaign\n  structure) — not a question with one fixed answer.\n- It's a **strategy question** that's faster to iterate on live than over\n  several back-and-forth messages.\n\n**Signal to watch for:** if you catch yourself writing \"it depends, we'd need\nto look at it live\" more than once in the same conversation, that's the cue\nto book a call instead of continuing to message.\n\n## Just message support when\n\n- It's a **factual question with a clear, documented answer**.\n- It's **troubleshooting where the cause can be diagnosed** from what's sent\n  (screenshots, logs, IDs) — no back-and-forth needed to see it.\n- It's **anything product/how-to related**.\n\n## Booking a call\n\n- Link: https://calendar.app.google/T8bxZ6Tp3foVAncm9\n- Available hours: **4:30 PM – 9:30 PM CET**\n- For everything else: `support@appstack.tech`\n"
}