Update to CardShow

{
  "description": "Compare upcoming CardShow events against a collector's dates, place, saved plans, seller-declared coverage, and optional connected HobbyWise Hunt List. Use when a user asks which card show to attend, wants events near a place or during a date range, asks where they are most likely to find their targets, or wants a transparent shortlist instead of a generic directory search.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 526
    }
  ],
  "name": "cardshow-find-my-best-show",
  "skill_md_contents": "---\nname: cardshow-find-my-best-show\ndescription: Compare upcoming CardShow events against a collector's dates, place, saved plans, seller-declared coverage, and optional connected HobbyWise Hunt List. Use when a user asks which card show to attend, wants events near a place or during a date range, asks where they are most likely to find their targets, or wants a transparent shortlist instead of a generic directory search.\n---\n\n# Find the best CardShow event\n\nRecommend events from CardShow evidence and the collector's own priorities. Keep the ranking explainable and never turn seller declarations into inventory guarantees.\n\n## Establish the search\n\n1. Resolve the intended place and date range. State exact dates when the user uses relative language such as “this weekend.”\n2. Ask a follow-up only when the missing place or date would materially change the result.\n3. Use `cardshow_get_my_planning` when signed-in saves or existing plans are relevant.\n4. Use `cardshow_find_events` for the bounded public candidate set.\n5. When the customer has the required CardShow access and approved HobbyWise connection, use `cardshow_recommend_events_for_my_hunt_list` for the same place and dates.\n6. If Hunt List access is unavailable, continue with public CardShow discovery and user-stated priorities. Do not infer or request private HobbyWise fields.\n\n## Compare the evidence\n\n- Use `cardshow_get_show_supply` for a selected event or a small set of serious candidates when the Hunt List recommendation did not already provide enough seller evidence.\n- Separate exact seller-listed item matches, strong category matches, and general leads.\n- Consider date and place fit, current saved/planned state, matched targets, declared category coverage, and how complete the seller information is.\n- Do not invent distance, travel time, admission cost, vendor count, inventory, verification, or availability when CardShow did not return it.\n- Do not rank an event first merely because it appears first in a tool result.\n\n## Present the shortlist\n\nReturn a compact comparison with:\n\n1. the best one to three events for the stated goal;\n2. the evidence supporting each choice;\n3. the important tradeoffs or missing information;\n4. unmatched Hunt List targets when available; and\n5. the CardShow notice that seller declarations are planning leads, not guarantees or reservations.\n\nIf no event has meaningful evidence, say so and show the best directory candidates without pretending they match.\n\n## Save only after confirmation\n\nDo not save, unsave, or change attendance during comparison. If the user asks to save or set attendance, refresh the exact show and current planning state, preview the exact final state, ask for explicit confirmation, use the matching final-state tool, and verify with a fresh read. Never apply a bulk action to multiple shows under vague confirmation.\n"
}