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

dispatch

Skill0 starsChanged 28 days agoMITView on GitHub

Routes football analytics requests to the right 2-3 skills. Load this FIRST when an NFL, FBS or FCS data or betting-analytics request arrives and you are unsure which skills to activate. Prevents loading all skills when only a few are needed.

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

1 rule. 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Never invent a tool. If it is not in endzoneapi-tool, it does not exist.

    line 125

“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. Load those skills. Do not load everything.

Default data tool: endzoneapi-tool. Load it alongside the analysis skill whenever a call is needed, for the exact names, parameters and credit costs.

Free tier: 500 credits every month at https://endzoneapi.com/signup.

Where Does the Question Live?

SignalLeague route
Team names like Chiefs, Bills; "NFL"; weeks 1 to 18NFL (default)
Ranked teams, bowls, "college football", FBScollege-football (route /v1/ncaaf/)
FCS, Montana State, Big Skycollege-football (route /v1/fcs/)

Persona Detection

SignalPersonaStart With
"Who plays this week?" / exploringExplorergame-lookup + endzoneapi-tool
"How good is this offense?"Analystepa-analysis + endzoneapi-tool
"I want to build a model"Builderfeature-engineering + walk-forward-validation
"Is there an edge on Sunday?"Bettorodds-explorer + edge-detection
"Is my model any good?"Validatorwalk-forward-validation + probability-calibration
"I am new to betting"New bettorodds-analysis + odds-explorer

Request Patterns to Skills

"Who plays Sunday?" / "What was the score?" / "Standings" / "Playoff seeds"

  1. game-lookup
  2. endzoneapi-tool for get_games, get_schedule, get_standings

"Preview Bills at Chiefs" / "Who has the edge in this game?"

  1. game-preview
  2. epa-analysis for the efficiency comparison
  3. odds-explorer if the user wants book-level prices

"Which offense is best?" / "Third-down EPA" / "Success rate" / "Play action"

  1. epa-analysis
  2. endzoneapi-tool

"Tell me about [player]" / "Who leads in receiving yards?" / "Target share"

  1. player-scouting
  2. next-gen-stats if separation, time to throw, pressure or rush yards over expected come up

"Does he get open?" / "Time to throw" / "Rush yards over expected" / "Drops"

  1. next-gen-stats
  2. player-scouting for counting stats

"What is the line?" / "Best price" / "How did it move?" / "Alternate spread"

  1. odds-explorer
  2. odds-analysis for devig or implied probability

"What does -150 mean?" / "Remove the vig" / "Fair price" / "Break-even rate"

  1. odds-analysis

"Is this bet +EV?" / "How much to stake?"

  1. edge-detection
  2. odds-analysis
  3. probability-calibration if probabilities come from a model

"Would this strategy have worked?" / "Backtest" / "CLV"

  1. backtesting
  2. walk-forward-validation
  3. odds-analysis

"Will he go over 250.5?" / "Anytime TD price" / "Prop history"

  1. prop-modeling
  2. player-scouting for role, odds-analysis for the price

"Build me a model" / "What features?" / "Elo"

  1. feature-engineering
  2. walk-forward-validation
  3. probability-calibration after predictions exist

"Is my model overconfident?" / "Brier score"

  1. probability-calibration
  2. walk-forward-validation

"College football" / "Ranked teams" / "Bowl lines" / "FCS"

  1. college-football
  2. odds-explorer for lines, same math applies
  3. Warn early that college has no EPA, tracking, injuries or depth charts

"How much will this cost?" / "Which tool?" / "REST or MCP?"

  1. endzoneapi-tool

Multi-Skill Workflows

Weekly betting card:

  1. game-lookup for the slate (2 credits)
  2. game-preview on the games of interest
  3. edge-detection where a model disagrees with the market
  4. odds-explorer to place the best price

Build and validate a model:

  1. feature-engineering
  2. walk-forward-validation
  3. probability-calibration
  4. backtesting

Prop session:

  1. player-scouting for role
  2. prop-modeling for the projection and price
  3. odds-analysis to devig

Credit Awareness

Before loading a skill that will make several calls, estimate the cost and say it. Expensive calls: get_line_movement (25), get_odds for a season (10 per game), get_plays (10 per page), get_player_props for many games (10 each). A season of consensus lines through get_games is 5. Use estimate_only on get_odds and get_player_props when a pull could be large.

Rules the Whole Pack Follows

  • Edges are estimates. No guarantees, no "locks".
  • Beating the closing line over many bets is better evidence than winning a few.
  • Small samples first: say n.
  • Never invent a tool. If it is not in endzoneapi-tool, it does not exist.

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.

Reviews can't be read right now.

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