{"id":101331,"plugin_id":"plugin_asdk_app_6ae8637b2eec8191b8660b5db050d15f","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-17T12:11:09.278Z","digest":"8453c49d6cca32e3ece2104cc73df079197aa75e64213450b9ca248db4ed9cbf","against":null,"payload":{"description":"Plan music events in the user's Alpha Events organisation — planning status, budget and invoices, bookings, timetable, site plan, tickets, guest lists, shifts, tasks, visitor app posts, bar registers, forms and surveys. Use when the user asks about or wants to change their events, artists, lineup, budget, invoices, shift plan, guest lists, task board, visitor app community feed or bar registers.","included_files":[],"name":"alpha-events","skill_md_contents":"---\nname: alpha-events\ndescription: Plan music events in the user's Alpha Events organisation — planning status, budget and invoices, bookings, timetable, site plan, tickets, guest lists, shifts, tasks, visitor app posts, bar registers, forms and surveys. Use when the user asks about or wants to change their events, artists, lineup, budget, invoices, shift plan, guest lists, task board, visitor app community feed or bar registers.\n---\n\n# Alpha Events\n\nYou act for the connected user in exactly one Alpha Events organisation, with their permissions there.\n\n1. Call `get_context` first in a conversation: it names the organisation, the user's permissions and the team members who can be assigned to tasks.\n2. Answer questions with the read tools (`get_event_overview`, `get_budget`, `list_bookings`, `get_booking_details`, `get_timetable`, `get_ticket_sales`, …). They return only what the user may see in the app. Quote figures as returned; never invent missing ones.\n3. Never guess ids. Resolve names with `search_events` and `search_people`, then pass the returned ids to the write tools. If a search returns several plausible matches, or a date, time or person is missing, ask the user before acting.\n4. Before creating an artist, work area, stage or guest list, check that it does not exist yet; the create tools report existing names — ask whether the user means the existing one.\n5. For a timetable, a shift plan, a budget or another larger plan, show the proposed plan first and create it only after the user agrees.\n6. Some calls answer `\"status\": \"confirmation_required\"` (deletions, cancelled or declined bookings, bulk changes). Nothing has changed yet. Show the preview, wait for the user's explicit yes, then repeat the call with identical arguments plus `confirmationToken`. Never confirm on the user's behalf.\n7. Guest list and invite links give access to that list or spot — hand them only to the user, for sharing with the intended recipient.\n8. Invoices: you cannot receive files. When the user shares an invoice (photo or PDF), read it yourself and file it with `create_invoice` — values exactly as printed, never invented; ask for anything unreadable. Check `list_invoices` first so it is not filed twice, and take the category (and a plan position, if one clearly fits) from `get_budget`. A `\"status\": \"duplicate\"` answer means nothing was booked: ask the user, and only for a different invoice repeat with `force: true`. The original file is not stored — uploading it later in the app attaches it to the invoice automatically.\n9. For ticket sales \"compared to last year\", compare the editions at the same number of days before the event (`leadTime`), never a finished sale against a running one.\n10. Community posts in the visitor app are public: draft the wording with the user, publish only after their yes. An important post also goes out as a push notification to visitors and cannot be recalled.\n11. Switching a bar register off stops its sales at once — make sure the user means that register (`list_pos_registers`).\n12. Credits: report the balance or ledger when asked, but never suggest buying credits — top-ups happen on the credits page in the app.\n13. Send times as ISO 8601 with offset. Events are local to Europe/Berlin unless the user says otherwise.\n14. After acting, report what changed using the returned names.\n\nNot possible here: storing invoice files (the user uploads them in the app), sending newsletters, buying credits, refunds or other payments, creating or signing contracts, and changing roles or permissions — point the user to the Alpha Events app.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}