← ClaudeAtlas

online-casino-councillisted

Convene the Online Casino Council, a panel of opinionated online casino personas (Hard Number CFO, Casino Director, External Consultant, Head of Product & Game Portfolio and Head of Compliance & RG, plus experts picked for the problem, the Gaming Board itself among them) that critiques a decision, names the risks, and places bets on the outcome. Use it for any online casino decision, even when the user does not say "council" — market entry, licence applications, game provider contracts, bonus and loyalty design, VIP programmes, affiliate deals, marketing budgets and channel mix, platform or vendor choices, payments, AI initiatives. Trigger on "casino council", "stress-test this", "what do you think of this plan", "should we launch in", "is this deal any good", or a pasted casino plan or budget. First run sets itself up with five questions.
vegasbrianc/online-casino-council · ★ 1 · DevOps & Infrastructure · score 65
Install: claude install-skill vegasbrianc/online-casino-council
# Online Casino Council A decision goes in. A panel of opinionated casino operators each attacks it. An orchestrator reconciles the disagreement into one recommendation with a bet attached. Adapted from Zapier's [War Council](https://github.com/zapier/wade-skills/blob/main/skills/war-council/SKILL.md) for online gambling, where the numbers are NGR not revenue, the customers are FTDs not sign-ups, and the regulator sits in every meeting whether invited or not. **Goal:** Replace "everyone in the room agrees with the boss" with a panel that is paid to disagree and speaks online casino natively. **Outcome:** A written Council Verdict — one-line answer, positions table, agreements, clashes, regulatory and player-harm exposure, the numbers the decision turns on, a conviction-weighted recommendation and a bet — saved as `council-verdicts/YYYY-MM-DD-online-casino-council-<slug>.md` beside the context file, or wherever its `Filing` block points. **Definition of done:** - [ ] Context file found, or created through the five setup questions, path reported - [ ] Framing confirmed with the decision-maker before any persona speaks - [ ] Market and licence status named in the framing - [ ] Council tier chosen and stated in the framing; seat count inside the cap - [ ] Every dynamic seat passed the two-question seating test, and the rest were named as excluded - [ ] At least one seat argued for the plan as written, or the verdict says why none would - [ ] Every member placed a bet with a c