{"id":6929,"plugin_id":"plugin_asdk_app_6a72d5743ab481918bff8de4f998ceb0","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T22:49:26.359Z","digest":"08fde57c600ab66c388ebb94a58d1436c756644af75c236123cf4292b543a81d","against":null,"payload":{"description":"Teach one poker concept through a concrete example from the user's current Poker app match when they ask to learn or understand ideas such as pot odds, position, ranges, effective stacks, stack-to-pot ratio, value betting, bluffing, or bet sizing. Use the model-visible ledger, stay focused on one concept, and avoid hidden-card spoilers unless requested.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":220}],"name":"poker-concept-from-match","skill_md_contents":"---\nname: poker-concept-from-match\ndescription: Teach one poker concept through a concrete example from the user's current Poker app match when they ask to learn or understand ideas such as pot odds, position, ranges, effective stacks, stack-to-pot ratio, value betting, bluffing, or bet sizing. Use the model-visible ledger, stay focused on one concept, and avoid hidden-card spoilers unless requested.\n---\n\n# Poker Concept From Match\n\nTeach one requested concept using a real decision from the current Poker widget's `modelContent`. Do not use `privateContent` or infer the undealt deck, burned cards, seeds, or random state.\n\n## Inputs\n\n- The concept the user wants to learn\n- The current match ledger, including hands, cards, boards, positions, blinds, stacks, pots, actions, and outcomes\n- An optional hand or decision the user wants used\n\nIf the concept is unclear, infer it from the user's wording when safe or ask one short question. If no suitable ledger is available, explain the concept briefly and state that a match-specific example requires the current rendered match. Do not start a new match unless the user asks to play.\n\n## Workflow\n\n1. Define the concept in plain language in one or two sentences.\n2. Select the clearest relevant decision from the requested hand or current match. Prefer a completed decision with enough recorded context to demonstrate the concept.\n3. Reconstruct only the facts needed for the lesson: street, position, user cards, public board, pot, effective stacks, prior action, and legal amounts.\n4. Show the calculation when the concept is quantitative. For pot odds, distinguish call cost from total pot; for wagers, distinguish chips added from `amountTo`; for stack-to-pot ratio, state the stack and pot used.\n5. Compare the actual choice with one useful alternative and explain the tradeoff using information available at that moment.\n6. End with a compact rule of thumb and one question the user can ask themselves in a future hand.\n\n## Hidden information\n\nTreat non-showdown opponent cards as spoilers. Do not reveal or use them in the main lesson unless the user explicitly asks for a spoiler or perfect-information explanation. Showdown cards may be discussed normally.\n\nIf spoilers are requested, preserve the decision-time lesson and add hindsight separately; do not rewrite a sound decision as a mistake merely because hidden cards made it lose.\n\n## Output\n\nUse this compact structure:\n\n1. Concept\n2. Example from the match, citing the hand number\n3. Calculation or reasoning\n4. Actual choice versus one alternative\n5. Rule of thumb\n\nKeep the lesson focused on one concept unless the user explicitly requests a broader tutorial.\n\n## Boundaries\n\n- Keep examples educational and confined to play-money poker.\n- Label equity, ranges, and behavioral reads as estimates unless directly established by the ledger or an explicit calculation.\n- Do not claim solver output, live external data, or access to other match instances.\n- Do not control the widget or alter gameplay.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}