Update to CardShow

{
  "description": "Build and optionally apply a practical private plan for one exact CardShow event. Use when a user asks for a show-day brief, checklist, seller stops, target plan, packing reminders, an event game plan, or help marking checklist items or attendance for a saved or selected show.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 529
    }
  ],
  "name": "cardshow-prepare-show-day",
  "skill_md_contents": "---\nname: cardshow-prepare-show-day\ndescription: Build and optionally apply a practical private plan for one exact CardShow event. Use when a user asks for a show-day brief, checklist, seller stops, target plan, packing reminders, an event game plan, or help marking checklist items or attendance for a saved or selected show.\n---\n\n# Prepare for a CardShow event\n\nTurn one exact event into a useful collector plan. Keep suggestions separate from stored CardShow facts and make every write deliberate.\n\n## Resolve the exact show\n\n1. Use `cardshow_get_my_planning` when the user refers to a saved show or existing plan.\n2. Use `cardshow_find_events`, `search`, or `fetch` when the show must be identified.\n3. If multiple shows remain plausible, ask the user to choose. Never guess the show ID.\n4. Call `cardshow_get_show_day_brief` with the exact show UUID before proposing a plan.\n\n## Build the brief\n\nOrganize the result into:\n\n- event facts and timing returned by CardShow;\n- current attendance and private plan;\n- remaining plan items;\n- relevant seller, category, and featured-item leads;\n- practical reminders; and\n- uncertainties the collector should verify.\n\nWhen an approved HobbyWise Hunt List is available, call `cardshow_recommend_events_for_my_hunt_list` for the show's place and dates and use only the result for this exact event. Otherwise, use existing CardShow plan items, seller declarations, and targets the user states in the conversation.\n\nDo not claim a seller will attend with a particular item unless the returned show supply says so. Even then, describe it as seller-declared and unverified, not reserved or guaranteed. Do not invent prices, appraisals, travel times, floor locations, or opening hours.\n\n## Propose a useful checklist\n\nPrefer a short ordered checklist over a long generic list:\n\n1. highest-priority targets or seller stops;\n2. questions or evidence to verify;\n3. items to bring;\n4. budget or trade guardrails only when the user supplied them; and\n5. logistical reminders supported by the show record or the user's instructions.\n\nPresent the proposed plan before changing CardShow.\n\n## Confirm and apply\n\n1. Refresh `cardshow_get_show_day_brief` and current planning.\n2. Preview the exact show, plan status, notes, every new item, and any attendance change.\n3. Ask for explicit confirmation of the complete effect.\n4. Use `cardshow_upsert_show_plan` only for the confirmed private plan. It preserves existing items and avoids duplicate matching items on retry.\n5. Use `cardshow_set_show_attendance` only for a separately listed confirmed final attendance state.\n6. Re-read the show-day brief and report the stored result.\n\nFor completion changes, refresh planning, use the exact returned item ID, preview complete or incomplete, confirm it, call `cardshow_set_show_plan_item`, and verify. Never invent an item ID or mark a target found merely because a seller declared a category.\n"
}