SKILL.md
FastF1 — Formula 1 Data
Before writing queries, consult references/api-reference.md for endpoints, ID conventions, and data shapes.
Quick Start
Prefer the CLI — it avoids Python import path issues:
sports-skills f1 get_race_schedule --year=2025
sports-skills f1 get_race_results --year=2025 --event=Monza
Python SDK (alternative):
from sports_skills import f1
schedule = f1.get_race_schedule(year=2025)
results = f1.get_race_results(year=2025, event="Monza")
CRITICAL: Before Any Query
CRITICAL: Before calling any data endpoint, verify:
- Year is derived from the system prompt's
currentDate— never hardcoded. - In January or February, use
year = current_year - 1(pre-season; the new F1 season has not started yet).
Choosing the Year
Derive the current year from the system prompt's date (e.g., currentDate: 2026-02-16 → current year is 2026).
- If the user specifies a year, use it as-is.
- If the user says "latest", "recent", "last season", or doesn't specify: The F1 season runs roughly March–December. If the current month is January or February, use
year = current_year - 1. From March onward, use the current year.
Workflows
Race Weekend Analysis
getraceschedule --year=<year>— find the event name and dategetraceresults --year=<year> --event=<name>— final classification (positions, times, points)getlapdata --year=<year> --event=<name> --session_type=R— lap-by-lap pace analysisgettireanalysis --year=<year> --event=<name>— strategy breakdown (compounds, stint lengths, degradation)
Driver/Team Comparison
getchampionshipstandings --year=<year>— championship context (points, wins, podiums)getteamcomparison --year=<year> --team1=<t1> --team2=<t2>ORgetdrivercomparison --year=<year> --driver1=<d1> --driver2=<d2>getseasonstats --year=<year>— aggregate performance (fastest laps, top speeds)
Season Overview
getraceschedule --year=<year>— full calendar with dates and circuitsgetchampionshipstandings --year=<year>— driver and constructor standingsgetseasonstats --year=<year>— season-wide fastest laps, top speeds, points leadersgetdriverinfo --year=<year>— current grid (driver numbers, teams, nationalities)
Commands
| Command | Description |
|---|---|
getraceschedule |
Full season calendar with dates and circuits |
getraceresults |
Final race classification (positions, times, points) |
getsessiondata |
Raw session info (Q, FP1, FP2, FP3, R) |
getdriverinfo |
Driver details from the grid |
getteaminfo |
Team info with driver lineup |
getlapdata |
Lap-by-lap timing with sectors and tire data |
getpitstops |
Pit stop durations and team averages |
getspeeddata |
Speed trap and intermediate speed data |
getchampionshipstandings |
Driver and constructor championship standings |
getseasonstats |
Aggregate season performance |
getteamcomparison |
Team head-to-head: qualifying, race pace, sectors |
getdrivercomparison |
Driver head-to-head: qualifying H2H, race H2H, pace delta |
gettireanalysis |
Tire strategy, stint lengths, degradation rates |
See references/api-reference.md for full parameter lists and return shapes.
Examples
Example 1: F1 calendar User says: "Show me the F1 calendar" Actions:
- Derive year from
currentDate - Call
getraceschedule(year=<derived_year>)
Result: Full calendar with event names, dates, and circuits
Example 2: Driver race performance User says: "How did Verstappen do at Monza?" Actions:
- Derive year from
currentDate(or from context) - Call
getraceresults(year=<year>, event="Monza")for final classification - Call
getlapdata(year=<year>, event="Monza", session_type="R", driver="VER")for lap times
Result: Finishing position, gap to leader, fastest lap, and tire strategy
Example 3: Latest results queried in pre-season User says: "What were the latest F1 results?" (asked in February 2026) Actions:
- Current month is February → season not yet started → use
year = 2025 - Call
getraceschedule(year=2025)to find the last event of that season - Call
getraceresults(year=2025, event=<last_event>)for the final race results
Result: Results of the final 2025 race
Commands that DO NOT exist — never call these
/getqualifying— does not exist. Usegetpracticegetsessiondatawithsessiontype="Q"for qualifying orsessiontype="FP1"/"FP2"/"FP3"for practice.— does not exist. Usegetstandingsgetchampionship_standingsinstead.— does not exist. Usegetresultsgetrace_resultsinstead.— does not exist. Usegetcalendargetrace_scheduleinstead.
If a command is not listed in the Commands table above, it does not exist.
Troubleshooting
Error: Event name not found Cause: Event name spelling does not match FastF1's internal naming Solution: Call getraceschedule(year=<year>) first to get the exact event names, then retry with the correct name
Error: Session data is empty Cause: The session has not happened yet Solution: FastF1 only returns data for completed sessions. Check getraceschedule for when the session is scheduled
Error: getraceresults returns no fastestlaptime Cause: Some races do not include fastest lap data in the results endpoint Solution: Use getlapdata(sessiontype="R") and find the minimum laptime across all drivers
Error: Querying the current year in January or February returns no data Cause: The new F1 season has not started yet Solution: Use year = current_year - 1 for any pre-March query; do not query the current year before March