agentleFS
Sign inStart free
noahowshnoahowsh/birdieapi-mcp/skills/dispatch/SKILL.md

dispatch

Skill0 starsChanged 28 days agoMITView on GitHub

Routes golf analytics requests to the right 2-3 skills. Load this FIRST when a golf data or betting-analytics 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.

40 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use orchestrate, spec and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • varun29ankuSSkill

    orchestrate

    This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.

    Also in 4 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not name a pick without the caveats from outright-model

    line 95
  2. Very specific:

    Before a multi-call plan, add up the credits from birdieapi-tool and tell the user.

    line 120

“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill Dispatch Guide

Match the request to a pattern below, load those skills, and stop. Always load birdieapi-tool alongside any skill that needs live data.

Scope check first

BirdieAPI 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.

First-use persona detection

SignalPersonaStart With
"Who won last week?" / "What is on this week?"Explorertournament-lookup
"How is Scheffler playing?"Scoutplayer-scouting + strokes-vs-field
"Who should I back at the Masters?"Outright bettortournament-preview + odds-explorer
"Build me a model of who wins"Builderoutright-model + feature-engineering
"Is my model any good?"Validatorwalk-forward-validation + probability-calibration
"What does a +2000 price mean?"New bettorodds-analysis

Request patterns -> skills

"Who won?" / "Results of the 2024 Masters" / "What is on this week?"

  1. tournament-lookup
  2. birdieapi-tool: list_tournaments, get_schedule, get_leaderboard

"Tell me about Rory McIlroy" / "Compare Scheffler and Schauffele"

  1. player-scouting
  2. strokes-vs-field if the user wants form or ratings

"Who is playing best?" / "What is a rating of 2.0?" / "Field-strength adjusted"

  1. strokes-vs-field
  2. birdieapi-tool: get_ratings, get_player_results

"Who is best on par 5s?" / "Which holes play hardest?" / "Birdie rate"

  1. hole-scoring
  2. course-fit if a specific course is involved

"Who plays well at Augusta?" / "Course history" / "Course fit"

  1. course-fit
  2. hole-scoring for the hole-level view of the course

"Preview the PGA Championship" / "Who are the contenders?"

  1. tournament-preview
  2. odds-explorer for the market side
  3. course-fit if there is time and the credit budget

"What are the odds?" / "Which book has the best price on Scheffler?" / "How did the price move?"

  1. odds-explorer
  2. odds-analysis for implied probability and devigging

"Devig this" / "What is 2000 worth as a probability?" / "Overround"

  1. odds-analysis

"Build a winner-probability model" / "Simulate the Open"

  1. outright-model
  2. feature-engineering for inputs
  3. walk-forward-validation before trusting any output

"Walk-forward" / "Is k-fold okay?" / "Leakage"

  1. walk-forward-validation
  2. feature-engineering

"Are my probabilities calibrated?" / "Brier" / "Log loss"

  1. probability-calibration

"Is there an edge?" / "Kelly" / "EV on a longshot"

  1. edge-detection (needs a model probability; if none, route to outright-model)
  2. odds-explorer for the price
  3. probability-calibration to check the probability first

"Backtest" / "Has this worked in past majors?" / "Track my bets"

  1. backtesting
  2. birdieapi-tool: get_winner_odds

"How do I call this?" / "What does it cost?" / "Which tool?"

  1. birdieapi-tool

"How does the LPGA / LIV / DP World Tour / Korn Ferry work here?"

  1. birdieapi-tool for the league argument and what each tour holds
  2. tournament-lookup or strokes-vs-field for the actual question
  3. Remember: no hole-by-hole outside the PGA Tour and Korn Ferry Tour, no odds outside the four men's majors

"Who will win the [major]?"

  1. tournament-preview for the picture
  2. outright-model for probabilities with a sensitivity range
  3. odds-explorer for the market, then odds-analysis to devig it
  4. Do not name a pick without the caveats from outright-model

Common chains

GoalChain
Preview a majortournament-lookup -> course-fit -> tournament-preview -> odds-explorer
Build and test a modelfeature-engineering -> outright-model -> walk-forward-validation -> probability-calibration
Decide whether a price is valueodds-explorer -> odds-analysis -> outright-model -> edge-detection
Test a betting ruleodds-explorer -> backtesting -> walk-forward-validation

Things the data cannot answer

Say this first, then route to the nearest skill:

RequestNot in the dataNearest skill
Live scores, tee times, weatherNext-morning data onlytournament-lookup for the finished rounds
Strokes gained off the tee, approach, puttingNo shot datahole-scoring, strokes-vs-field
Round, matchup or top-10 oddsOnly major winner pricesodds-explorer
Each-way termsNot heldodds-analysis for the outright
LIV team standingsIndividual results onlytournament-lookup

Credit-aware routing

Before 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).

When NOT to Use This Guide

Single-skill requests do not need dispatch. "Devig +450 / +900 / +1200" goes straight to odds-analysis.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free