Update to BirdieAPI

{
  "description": "Routes golf analytics requests to the right 2-3 skills. Load this FIRST when a golf data request comes in and you are unsure which skills to activate. Prevents loading all 16 skills when only 2-3 are needed. Do not use when the request clearly names one skill's job, such as devigging a price -- load odds-analysis directly.",
  "included_files": [],
  "name": "dispatch",
  "skill_md_contents": "---\nname: dispatch\ndescription: \"Routes golf analytics requests to the right 2-3 skills. Load this FIRST when a golf data request comes in and you are unsure which skills to activate. Prevents loading all 16 skills when only 2-3 are needed. Do not use when the request clearly names one skill's job, such as devigging a price -- load odds-analysis directly.\"\nmetadata:\n  version: 1.0.0\n  author: BirdieAPI\n---\n\n# Skill Dispatch Guide\n\nMatch the request to a pattern below, load those skills, and stop. Always load `birdieapi-tool` alongside any skill that needs live data.\n\n## Scope check first\n\nBirdieAPI covers the PGA Tour, LPGA, LIV, DP World Tour and Korn Ferry Tour as historical and next-morning data. The only odds are the winner prices of the four men's majors. If the user wants live scores, tee times, weather, round or matchup odds, top-10 markets or each-way terms, say it is not in the data and offer the nearest thing that is.\n\n## First-use persona detection\n\n| Signal | Persona | Start With |\n|--------|---------|-----------|\n| \"Who won last week?\" / \"What is on this week?\" | **Explorer** | `tournament-lookup` |\n| \"How is Scheffler playing?\" | **Scout** | `player-scouting` + `strokes-vs-field` |\n| \"Who should I back at the Masters?\" | **Odds reader** | `tournament-preview` + `odds-explorer` |\n| \"Build me a model of who wins\" | **Builder** | `outright-model` + `feature-engineering` |\n| \"Is my model any good?\" | **Validator** | `walk-forward-validation` + `probability-calibration` |\n| \"What does a +2000 price mean?\" | **Odds reader** | `odds-analysis` |\n\n## Request patterns -> skills\n\n### \"Who won?\" / \"Results of the 2024 Masters\" / \"What is on this week?\"\n1. `tournament-lookup`\n2. `birdieapi-tool`: `list_tournaments`, `get_schedule`, `get_leaderboard`\n\n### \"Tell me about Rory McIlroy\" / \"Compare Scheffler and Schauffele\"\n1. `player-scouting`\n2. `strokes-vs-field` if the user wants form or ratings\n\n### \"Who is playing best?\" / \"What is a rating of 2.0?\" / \"Field-strength adjusted\"\n1. `strokes-vs-field`\n2. `birdieapi-tool`: `get_ratings`, `get_player_results`\n\n### \"Who is best on par 5s?\" / \"Which holes play hardest?\" / \"Birdie rate\"\n1. `hole-scoring`\n2. `course-fit` if a specific course is involved\n\n### \"Who plays well at Augusta?\" / \"Course history\" / \"Course fit\"\n1. `course-fit`\n2. `hole-scoring` for the hole-level view of the course\n\n### \"Preview the PGA Championship\" / \"Who are the contenders?\"\n1. `tournament-preview`\n2. `odds-explorer` for the market side\n3. `course-fit` if there is time and the credit budget\n\n### \"What are the odds?\" / \"Which book has the best price on Scheffler?\" / \"How did the price move?\"\n1. `odds-explorer`\n2. `odds-analysis` for implied probability and devigging\n\n### \"Devig this\" / \"What is 2000 worth as a probability?\" / \"Overround\"\n1. `odds-analysis`\n\n### \"Build a winner-probability model\" / \"Simulate the Open\"\n1. `outright-model`\n2. `feature-engineering` for inputs\n3. `walk-forward-validation` before trusting any output\n\n### \"Walk-forward\" / \"Is k-fold okay?\" / \"Leakage\"\n1. `walk-forward-validation`\n2. `feature-engineering`\n\n### \"Are my probabilities calibrated?\" / \"Brier\" / \"Log loss\"\n1. `probability-calibration`\n\n### \"How do I call this?\" / \"What does it cost?\" / \"Which tool?\"\n1. `birdieapi-tool`\n\n### \"How does the LPGA / LIV / DP World Tour / Korn Ferry work here?\"\n1. `birdieapi-tool` for the `league` argument and what each tour holds\n2. `tournament-lookup` or `strokes-vs-field` for the actual question\n3. Remember: no hole-by-hole outside the PGA Tour and Korn Ferry Tour, no odds outside the four men's majors\n\n### \"Who will win the [major]?\"\n1. `tournament-preview` for the picture\n2. `outright-model` for probabilities with a sensitivity range\n3. `odds-explorer` for the market, then `odds-analysis` to devig it\n4. Do not name a pick without the caveats from `outright-model`\n\n## Common chains\n\n| Goal | Chain |\n|------|-------|\n| Preview a major | `tournament-lookup` -> `course-fit` -> `tournament-preview` -> `odds-explorer` |\n| Build and test a model | `feature-engineering` -> `outright-model` -> `walk-forward-validation` -> `probability-calibration` |\n\n## Things the data cannot answer\n\nSay this first, then route to the nearest skill:\n\n| Request | Not in the data | Nearest skill |\n|---------|------------------|---------------|\n| Live scores, tee times, weather | Next-morning data only | `tournament-lookup` for the finished rounds |\n| Strokes gained off the tee, approach, putting | No shot data | `hole-scoring`, `strokes-vs-field` |\n| Round, matchup or top-10 odds | Only major winner prices | `odds-explorer` |\n| Each-way terms | Not held | `odds-analysis` for the outright |\n| LIV team standings | Individual results only | `tournament-lookup` |\n\n## Credit-aware routing\n\nBefore a multi-call plan, add up the credits from `birdieapi-tool` and tell the user. A preview is about 40 to 60 credits. A backtest across every major in the odds archive is one `get_winner_odds` call per major (5 credits each) plus the leaderboards (2 each).\n\n## When NOT to Use This Guide\n\nSingle-skill requests do not need dispatch. \"Devig +450 / +900 / +1200\" goes straight to `odds-analysis`.\n"
}