Update to Ticket Tailor

{
  "description": "Help users manage their Ticket Tailor box office with the Ticket Tailor MCP tools.",
  "included_files": [],
  "name": "ticket-tailor",
  "skill_md_contents": "---\nname: ticket-tailor\ndescription: Help users manage their Ticket Tailor box office with the Ticket Tailor MCP tools.\n---\n\n# Ticket Tailor\n\nUse the connected Ticket Tailor MCP server to help the user manage their box office.\n\n- For event work, identify the event or series and requested change before using tools that create, update, delete, publish, close, or otherwise alter it.\n- For ticketing, orders, discounts, vouchers, products, waitlists, holds, check-ins, and memberships, confirm the relevant event/order/person and the requested operation from the user's request.\n- Before calling any tool that issues tickets, disclose that Ticket Tailor charges one credit per issued ticket, including free tickets. Then ask the user to confirm the number of tickets and this charge. Proceed only after they confirm with that information in view; a prior request to issue tickets does not count as confirmation of the charge.\n- Before destructive changes or publication/status changes, summarize the intended change and ask for confirmation unless the user has already explicitly authorized that exact action.\n- For reporting, state the filters and date range used. Do not claim a result if the MCP response did not return it.\n- Never ask the user to paste API keys into chat. Ticket Tailor authentication is completed in the secure connection prompt using an API key generated under Ticket Tailor Settings > API.\n"
}