agentleFS
noahowshnoahowsh/birdieapi-mcp/skills/tournament-preview/SKILL.md

tournament-preview

Skill0 starsChanged 29 days agoMITView on GitHub

Builds a pre-tournament preview for a golf event: the course and its setup, the field's best players on rating and recent form, course record for the contenders, par-type strengths that suit the holes, and for the four men's majors the winner prices side by side. Use when the user asks for a preview of the Masters, PGA Championship, U.S. Open, Open Championship or any PGA Tour, LPGA, DP World Tour or Korn Ferry event, who the contenders are, or what to watch. Do not use for a single lookup -- see tournament-lookup or player-scouting. Do not use for devigging or stake sizing -- see odds-analysis and edge-detection.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Use as_of the day before play for a past preview so nothing after the event leaks in.

    line 74
  2. Distinctive:

    Put rating rank beside the latest pregame price.

    line 100

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Tournament Preview

Default data tool: BirdieAPI (birdieapi-tool). A preview is a compound skill that loads several tools. Budget about 40 to 60 credits. State the plan and the cost before pulling.

You are an expert golf analyst writing a preview. Your goal is a one-page read of who is playing well, who has a record here, what the course rewards, and (for majors) what the market thinks, with every claim sourced to a call and every caveat stated.

When to Use

  • "Preview this week's event."
  • "Who are the contenders at the PGA Championship?"
  • "Does the course suit a long hitter?" (the data supports par-type and hole-level reads, not driving distance by shot)

When NOT to Use

  • One fact (who won, a player's id) -- see tournament-lookup, player-scouting
  • Win probabilities -- see outright-model
  • Edge and staking -- see edge-detection

Commands Available

CommandWhat It DoesCredits
get_scheduleThe event, dates, course, defending champion1
list_tournamentsA prior edition's tournament_id, and cut data1
get_courseThe course as set up in a prior edition (par, yards, how each hole played)2
get_ratingsWho is playing best, with as_of for a past preview2
get_course_historyContenders' record at the event5 each
get_player_statsPar-type splits and ball-striking lines for a contender5 each
get_head_to_headTwo contenders against each other5
get_winner_oddsMajors only: prices by book5

Commands That Do NOT Exist

Not AvailableUse Instead
get_field, get_entry_listNot available for an upcoming event; use the priced golfers (majors) or ask the user
get_tee_times, get_pairings, get_weatherNot available; say so
get_preview, get_picksCompose it from the calls above
get_odds for non-majorsNot available; ask for the user's lines

How It Works

Step 1: Identify the event and the course.

get_schedule {"days": 14}

Rows give tournament_id, start_date, status, courses[] and defending_champion. For a past preview, use list_tournaments with the season.

Step 2: Describe the course from the last edition. The current week's setup is not published before play, so use the most recent edition on the same course.

get_course {"tournament_id": "401580344"}

Real response (2024 Masters): Augusta National, par 72, 7,555 yards, 298 rounds, scoring average 73.91. Hole 11 (par 4, 520 yards) ranked 1 in difficulty with a bogey rate of 0.2852; hole 13 (par 5, 545 yards) played to 4.758 with a birdie rate of 0.3624. Summarise: the hardest five holes, the number of par 5s that played under par, and the spread between the easiest and hardest. See hole-scoring.

Step 3: Who is playing well.

get_ratings {"as_of": "2024-04-04", "limit": 30}

Use as_of the day before play for a past preview so nothing after the event leaks in. For a live preview omit as_of. Real top of the list for the 2024 Masters:

1  Scottie Scheffler  2.88 (119 weighted rounds)
2  Jon Rahm           2.58 (114)
3  Xander Schauffele  2.48 (115)
4  Rory McIlroy       2.41 (91)
5  Patrick Cantlay    2.19 (101)

Step 4: Course record for the top 6 to 10.

get_course_history {"player_id": "9478", "tournament_id": "401580344"}

Seven starts, two wins, five top tens, average finish 7.9, +2.78 strokes versus the field per round at the event for Scheffler. Apply course-fit shrinkage before reading it as anything beyond form.

Step 5: Par-type fit. For two or three contenders, pull get_player_stats for the last full season and compare sg_par3, sg_par4 and sg_par5 with what the course rewards. These are score-based hole-type splits, not shot data.

Step 6: Market (majors only).

get_winner_odds {"tournament_id": "401580344", "limit": 10}

Put rating rank beside the latest pregame price. Real DraftKings latest prices against the ratings above:

Scheffler  +400   (20.0% raw)    rating 2.88
Rahm       +1200  (7.7% raw)     rating 2.58
Schauffele +2000  (4.8% raw)     rating 2.48
McIlroy    +1000  (9.1% raw)     rating 2.41
Cantlay    +2800  (3.4% raw)     rating 2.19

Raw implied probabilities include margin; devig before saying what the market believes (odds-analysis). A rating gap that the price does not reflect is a question to investigate, not a bet.

Step 7: Head-to-head, if the user cares. get_head_to_head for the two shortlisted contenders on the same season.

Step 8: Write it up. Short sections: Course, Form, Course record, Market, Risks. End with what the data cannot see: weather, injuries, withdrawals, wave draws, tee times.

Credit Usage

OperationCreditsNotes
Event + prior-edition course4get_schedule, get_course, list_tournaments
Ratings2
Course history, 6 players30
Winner prices (majors)5
Par-type splits, 3 players15
Full previewabout 56

On the free tier (500 credits a month) that is about nine previews.

Anti-patterns

What Claude Might DoWhy It's WrongDo This Instead
Name a "field" for an upcoming eventNot in the dataSay it is the priced golfers or the user's list
Use today's rating for a past previewLeakageas_of before round 1
Say "suits his driving"No driving by shot, only season lines and hole splitsState exactly what the splits show
Read a 4-start course record as destinyTiny sampleShow rounds and shrink
Give a pickThe data cannot see weather or injuriesPresent contenders with risks
Quote odds for a non-majorNot heldAsk for the user's own lines

Output Format

2024 Masters preview (Augusta National, par 72, 7,555 yards)
Course: hole 11 hardest (bogey rate 28.5%), holes 2 and 13 (par 5s) play under par; round scoring average 73.91 in 2024.
Form (rating as of 4 Apr 2024): Scheffler 2.88, Rahm 2.58, Schauffele 2.48, McIlroy 2.41.
Course record (strokes versus the field per round): Scheffler +2.78 over 7 starts (2 wins).
Market (DraftKings latest): Scheffler +400, McIlroy +1000, Rahm +1200. Raw, not devigged.
Not in the data: weather, tee times, injuries, the confirmed field.

What to Do Next

What You FoundNext ActionSkill
A contender listConvert to probabilitiesoutright-model
A price gapDevig and compareodds-analysis, edge-detection
A course questionHole-level detailhole-scoring

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.