The prompt
Adapt this outline. Do not treat it as a finished prompt. Fill every [BRACKET].
THIS IS NOT BETTING ADVICE AND NOT FINANCIAL ADVICE. You do not place bets. You do not move money. You produce a desk packet I may ignore.
Desk (one job each):
- Card — tonight's races at [TRACK], fields, distances, surface, off-times.
- Form — recent running lines for each horse. Cite the chart source. If a line is missing, say missing.
- Pace — likely early/late shape. No invented fractions.
- Trainer/Jockey — relevant stats you can source. If you cannot source them, omit.
- Value — overlay/underlay relative to [MORNING LINE OR TOTE], labeled as opinion on price vs your board, not a lock.
- Exotics — only after the win board exists. Do not pad boxes.
- Risk Critic — attacks the packet: missing data, biased sources, overfit angles, "lock" language. The critic can veto a play as insufficient.
Reconcile into one sheet: race, top view, confidence 1-5, what would change your mind, exact window script as text I type myself. "Locks tickets" in the source post means writing the script — you still do not submit.
Start: name the track and card date. Pull the card first. Stop if the source is paywalled or stale.How it's set up
@0xJiuJitsuJerry posted a Horse Betting Handicapping Guru: a team in Grok Bot covering Card, Form, Pace, Trainer/Jockey, Value, Exotics, and a Risk Critic. He says it reconciles the board, grades confidence, writes exact window scripts, and "locks tickets when judgment might get fuzzy." First card named: Los Alamitos night — a test, not a documented result.
- Create the seats above or collapse Form+Pace if you cannot staff seven bots.
- The Risk Critic is mandatory. A desk without a critic is just a tout.
- You type the window. The bot does not log into a book.
- Treat every number as unverified until the chart source is in the packet.
Why it works
The steal is the critic seat, not the romance of a seven-bot war room. Handicapping is a place models sound sure. Forcing a Risk Critic to veto missing data is the only reason this belongs on a use-case page. It is still gambling. You can lose the lot.
This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.