dispatch
Skill1 starsChanged 28 days agoMITView on GitHub
Routes tennis analytics requests to the right 2 or 3 skills. Load this FIRST when an ATP or WTA data or analytics request comes in and you are unsure which skills to activate. Prevents loading all 16 skills when only a few are needed. Also sets expectations on what the data cannot answer (serve statistics, in-play, props).
40 other projects use a version of this.
Adopted by
Most recently taken up by
- renzrollon/interlocktheir own version, first seen Nov 5, 2026
- dan-myles/skillstheir own version, first seen Nov 1, 2026
- bestony/skillstheir own version, first seen Nov 1, 2026
- AcKeskin/contexturetheir own version, first seen Nov 1, 2026
- mhlaghari/stuntmantheir own version, first seen Nov 1, 2026
- vu1n/pillboxtheir own version, first seen Oct 26, 2026
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.
varun29ankuSSkillorchestrate
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
SentrySkillspec
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
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 4 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 6 projects that use this
Other versions40 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 40
- your-papa/obsidian-Smart2Brain★ 1.3ksame name
- s2b-dev/smart-second-brain★ 1.3ksame name
- bassimeledath/dispatch★ 411same name
- renzrollon/interlock★ 61same name
- fagemx/edda★ 36same name
- phj128/autoworker★ 18same name
- clonable-eden/cekernel★ 17same name
- mhlaghari/stuntman★ 16same name
- YippeeXuXu/dsh-collab-mode★ 5same name
- BigY0shi/super-skills★ 4same name
30 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- acesapi-toolSkill
- backtestingSkill
- edge-detectionSkill
- feature-engineeringSkill
- head-to-head-analysisSkill
- match-lookupSkill
- match-previewSkill
- odds-analysisSkill
- odds-explorerSkill
- player-scoutingSkill
- probability-calibrationSkill
- ranking-historySkill
- set-score-modelingSkill
- surface-eloSkill
- walk-forward-validationSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
1
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
- Very specific: line 121
Use pre-match ratings only (rating.before), never rating.after.
- Distinctive: line 123
If a user asks for a lock, a guarantee or a pick to bet the house on, decline that framing and give the analysis.
“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.
Files
Skill Dispatch Guide
Match the request to a pattern below. Load those skills only.
Default data tool: acesapi-tool. It covers 13 tools for ATP and WTA singles. Load it alongside the strategy skill unless the request needs no data (user-supplied numbers).
Tour check first. ATP is the default. For WTA questions, every call needs "league": "wta". Ask which tour only if the player or event is ambiguous.
First-Use Persona Detection
| Signal | Persona | Start With |
| "What matches are on today?" / exploring | Explorer | match-lookup + acesapi-tool |
| "Tell me about this player" | Scout | player-scouting + ranking-history |
| "Who wins tomorrow?" | Previewer | match-preview + surface-elo |
| "I want to build a prediction model" | Builder | feature-engineering + surface-elo |
| "Is my model any good?" | Validator | walk-forward-validation + probability-calibration |
| "Where is the value?" / prices | Bettor | odds-explorer + edge-detection |
| "I am new to odds" | New Bettor | odds-analysis + odds-explorer |
Request Patterns -> Skills to Load
"Who plays today?" / "Who won?" / "Show me the draw" / "Every final this season"
match-lookup: results, schedules, drawsacesapi-tool:get_matches,get_schedule,get_tournament,list_tournaments
"Tell me about [player]" / "How is she doing?" / "Compare these two players"
player-scouting: profile, surface fit, opposition quality, formacesapi-tool:search_players,get_player,get_surface_splits,get_player_stats- Two players with a direct record: also
head-to-head-analysis
"[A] vs [B] head to head" / "Who leads the rivalry?" / "How do they split on clay?"
head-to-head-analysis: record, surface split, finals, weightingsurface-eloif a probability is wanted
"Who is number one?" / "Ranking on a date" / "How did the ranking change?"
ranking-history: lists, trajectories, points versus ranksurface-eloif the question is really about strength
"Who is best on clay?" / "Win probability for A vs B" / "How does the rating work?"
surface-elo: ratings, probability formula, blendinghead-to-head-analysisfor context if a rivalry exists
"Preview the match" / "Who is favored tomorrow and why?"
match-preview: assembles ratings, form, record, route, pricesurface-elofor the probabilityodds-explorerif the event is a Slam, Masters or WTA 1000
"What are the odds?" / "Best price" / "How did the line move?"
odds-explorer: prices, margins, open to closeodds-analysisfor devigging- Remember: odds exist only for Grand Slams (mid-2020 on) and Masters and WTA 1000 (August 2024 on)
"What probability does +450 imply?" / "Remove the vig" / "Shin vs power"
odds-analysis: no data needed unless prices must be fetched
"Is this a value bet?" / "My model says 62 percent" / "How much to stake?"
edge-detection: EV, CLV, fractional Kellyodds-explorerfor current pricesprobability-calibrationif the model probability is untested
"Would this strategy have worked?" / "ROI over a Slam" / "Is my edge real?"
backtesting: walk-forward simulation with closing lineswalk-forward-validationif the question is about model accuracy only- Warn about credits first (2 per priced match)
"How many games will the match go?" / "Straight sets chance" / "Tiebreak frequency"
set-score-modeling: set distributions, totals, tiebreakssurface-elofor the match probability that feeds it- State that serve data does not exist
"Build features" / "What should I feed the model?" / "Is there leakage?"
feature-engineering: pre-match ratings, form, rest, symmetric layoutwalk-forward-validationwhen evaluation comes next
"Cross-validation okay?" / "Compare two models" / "How many matches do I need?"
walk-forward-validation: time-ordered evaluation and significanceprobability-calibrationfor reliability
"Are my probabilities calibrated?" / "Overconfident on favorites"
probability-calibration: reliability tables, Platt, isotonicwalk-forward-validationfor the split
Things the Data Cannot Answer
Say so immediately and offer the closest proxy.
| Request | Reality | Offer |
| Aces, double faults, first-serve percentage, break points | No serve statistics exist | Games-won share, tiebreak record, total games per match (player-scouting, set-score-modeling) |
| Live or in-play prices | Pre-match open and close only | Open to close movement (odds-explorer) |
| Player props (aces, games won, sets) | No props data | Not supported: do not build a prop model |
| Injury or fitness reports | None | Rest days and recent load from scores (feature-engineering) |
| Prices for tour 250 and 500 events | Not covered | Ratings-only analysis |
| Rankings outside the top 100 to 150 | Not in the lists | Ratings via get_ratings for active players with 10 or more rated matches |
| Doubles | Singles only | State the limit |
Multi-Skill Workflows
Pre-match workflow: match-lookup (find the match) -> match-preview (brief) -> odds-explorer (price) -> edge-detection (only with a tested model).
Model workflow: feature-engineering -> walk-forward-validation -> probability-calibration -> backtesting.
Research workflow: ranking-history and surface-elo to find an anomaly (a rank far from rating) -> player-scouting to explain it -> head-to-head-analysis for the direct record.
Credit Awareness
Before any request that loops over many matches or players, state the number of calls and the credits (see acesapi-tool). Cheap by default: one preview is about 20 credits; a day of results is 2; odds for a Slam round of 64 matches is 128. The free tier is 500 credits a month with no card; plans and top-ups are on https://acesapi.com/pricing.
Rules for Every Answer
- Cite the tool results used, and name the tour.
- Use pre-match ratings only (
rating.before), neverrating.after. - Probabilities and edges are estimates. Mention variance and sample size, and prefer closing-line value over short-run results.
- If a user asks for a lock, a guarantee or a pick to bet the house on, decline that framing and give the analysis.
Anti-patterns
| What Claude Might Do | Why It's Wrong | Do This Instead |
| Load all 16 skills | Wastes context | 2 or 3 per request |
| Reach for a nonexistent odds tool | Odds are inside get_match | odds-explorer |
| Start betting analysis without checking coverage | Tour 250 events have no prices | Check the tournament tier |
| Skip the tour | WTA ids and ATP ids differ | Pass league |
| Answer serve questions | No data | Offer proxies |
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
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.