← FastballAPICONTENT HISTORY
WHAT CHANGED
Update to FastballAPI
Snapshot Oct 30, 2026 · 00:06 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save FastballAPI and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Routes a baseball analytics request to the right 2 to 3 skills in this pack. Load this FIRST when an MLB or college baseball data or analytics request comes in and you are unsure which skills to activate. Prevents loading all 16 skills when two will do. Do not use when the request already names one skill's job, such as devigging two prices: load odds-analysis directly.",
"included_files": [],
"name": "dispatch",
"skill_md_contents": "---\nname: dispatch\ndescription: \"Routes a baseball analytics request to the right 2 to 3 skills in this pack. Load this FIRST when an MLB or college baseball data or analytics request comes in and you are unsure which skills to activate. Prevents loading all 16 skills when two will do. Do not use when the request already names one skill's job, such as devigging two prices: load odds-analysis directly.\"\nmetadata:\n version: 1.0.0\n author: FastballAPI\n---\n\n# Skill Dispatch Guide\n\nMatch the request to a pattern, load those skills, stop. Always pair with `fastballapi-tool` when live data is needed: it holds the tool list, credit costs and the coverage limits.\n\n## First-Use Persona Check\n\n| Signal | Persona | Start with |\n|--------|---------|------------|\n| \"What happened last night?\" / exploring | Explorer | `game-lookup` |\n| \"Who is better, X or Y?\" / scouting | Scout | `player-scouting`, `pitch-mix-analysis` |\n| \"I want to build a model\" | Builder | `walk-forward-validation`, `pythagorean-record` |\n\n## Request Patterns\n\n### \"What was the score?\" / \"Who plays tonight?\" / \"Schedule\"\n1. `game-lookup`: `get_games`, `get_schedule`, `get_game`.\n2. Add `fastballapi-tool` only if you need cost or parameter detail.\n\n### \"How are the Dodgers doing?\" / \"Standings\" / \"Best team\" / \"Run differential\"\n1. `team-analysis`: standings, team stats, Elo.\n2. `pythagorean-record` if the question is luck, regression or \"are they as good as their record?\".\n\n### \"Tell me about Aaron Judge\" / \"Compare two hitters\" / \"Who leads the league in OPS?\"\n1. `player-scouting`: search, season lines, leaders, injuries.\n2. `run-value-analysis` if the user wants RE24 or clutch splits.\n3. `spray-chart-analysis` if the question is where he hits the ball.\n\n### \"What does Tarik Skubal throw?\" / \"Whiff rate by pitch\" / \"Pitch mix\"\n1. `pitch-mix-analysis`: `get_pitch_mix`, `get_pitches`.\n2. `player-scouting` for the season line behind it.\n\n### \"Run value\" / \"RE24\" / \"How much did that home run matter?\" / \"Hitting with runners in scoring position\"\n1. `run-value-analysis`: `get_plate_appearances`, `get_player`.\n\n### \"Where does he hit the ball?\" / \"Shift\" / \"Pull rate\" / \"Spray chart\"\n1. `spray-chart-analysis`: `get_spray_chart`.\n2. `player-scouting` for context.\n\n### \"Pythagorean record\" / \"Who got lucky?\" / \"Expected wins\"\n1. `pythagorean-record`: `get_standings`, `get_team_stats`.\n2. `team-analysis` for the surrounding picture.\n\n### \"What are the odds?\" / \"Best price\" / \"Did the line move?\"\n1. `odds-explorer`: `get_odds`, `get_line_movement`.\n2. `odds-analysis` for devigging and implied probability.\n\n### \"Preview tonight's Dodgers game\" / \"Game breakdown\"\n1. `game-preview`: composes standings, ratings, schedule, injuries and odds.\n2. `odds-explorer` only if the user wants the full book-by-book table.\n\n### \"Devig these odds\" / \"No-vig price\" / \"Implied probability\"\n1. `odds-analysis`. No data call needed for plain math.\n\n### \"Strikeout prop\" / \"Total bases over\" / \"Will he go over his hits line?\"\n1. `prop-modeling`: pitcher strikeouts, hits, total bases.\n\n### \"Backtest this\" / \"Would this have made money?\" / \"Closing line value\"\n2. `walk-forward-validation` for the model underneath.\n\n### \"Is my model accurate?\" / \"Cross-validation\" / \"Train/test split\" / \"Features\"\n1. `walk-forward-validation`: temporal splits, leakage, calibration check.\n\n### \"College baseball\" / \"Omaha\" / \"NCAA\"\n1. Route as above, then tell the user what college lacks (no pitch rows, no spray charts, no props, no injuries). `fastballapi-tool` has the full list.\n\n## Common Chains\n\n| Goal | Chain |\n|------|-------|\n| Scout a pitcher end to end | `player-scouting` (season line) then `pitch-mix-analysis` (arsenal) then `prop-modeling` (strikeout line) |\n| Understand a hitter's power | `player-scouting` then `spray-chart-analysis` then `run-value-analysis` |\n| Find out if a club is overrated | `team-analysis` then `pythagorean-record` |\n| Cover tonight's game | `game-preview` then `odds-explorer`, adding `prop-modeling` for a named player |\n\n## Ambiguity Resolver\n\n| The user says | They probably mean | Ask or assume |\n|---------------|--------------------|---------------|\n| \"The odds\" | Moneyline for a named game | Assume moneyline, show run line and total too |\n| \"His stats\" | Season batting or pitching line | Assume the latest completed season, say which |\n| \"Whiffs\" | Whiff rate per swing by pitch | `pitch-mix-analysis` |\n| \"Is he good?\" | Rate stats with a sample caveat | `player-scouting` |\n| \"Over/under\" | Game total, unless a player is named | Ask if unclear |\n| \"Last year\" | The most recent completed season | State the year |\n| \"Tonight\" | The next date with games in `get_schedule` | Check the date first |\n\n## Credit-Aware Routing\n\n| Request | Rough cost |\n|---------|-----------|\n| Scores for a date | 2 |\n| Standings and Pythagorean | 2 |\n| Pitcher arsenal (search + mix) | 6 |\n| Game preview | about 9 to 20 |\n| One day of odds | 10 |\n| Pitcher strikeout prop history | 11 |\n| Season of game-by-game odds | about 12,000: ask first |\n\nIf a 500-credit month will not cover the job, say so. Do not trim the method to fit.\n\n## Rules\n\n1. Two or three skills per request. More is noise.\n2. Never invent a tool. If a skill's \"Commands That Do NOT Exist\" table lists it, stay out.\n3. Say the data window before the answer when it matters (props start May 2023, win probability 2019, college has no pitch data).\n\n## When NOT to Use This Guide\n\nSingle-skill requests do not need routing. \"What was the Yankees score last night\" is `game-lookup`. \"Convert +150 to a probability\" is `odds-analysis`.\n"
}SHA-256 of public snapshot: c6e719b03c7dd5fb10f30c9af53d4968ad38c40686303cc61f334bb4507c7295