f1-cli
Query Formula 1 data using the f1-cli command-line tool (wraps OpenF1 API). Use when the user asks about F1 race results, lap times, driver standings, pit stops, telemetry, weather, team radio, overtakes, tire strategy, or any Formula 1 statistics. Also use when asked to compare drivers, analyze race performance, look up session data, or retrieve real-time F1 information. Triggers on mentions of F1, Formula 1, Grand Prix, specific driver names (Verstappen, Hamilton, Norris), or racing data queries. Even casual questions like "who won the last race" or "how fast was Max's fastest lap" should use this skill.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/barronlroth/f1-cliWhat This Skill Does
The f1-cli skill serves as a comprehensive interface for OpenClaw to interact with Formula 1 data. By wrapping the OpenF1 API, this skill allows the AI agent to retrieve real-time and historical racing statistics directly via a command-line interface. Whether you need to analyze high-frequency telemetry, verify tire strategies, or simply check the current driver championship standings, the f1-cli skill translates natural language requests into precise API queries. It acts as the bridge between your questions and the raw telemetry, lap data, and race control logs recorded during F1 Grand Prix weekends.
Installation
For Homebrew users, you can tap the repository and install directly:
brew tap barronlroth/tap && brew install f1-cli
If you prefer installing from source via Go, execute:
go install github.com/barronlroth/f1-cli/cmd/f1@latest
Ensure that the f1 binary is in your system PATH so that the OpenClaw agent can successfully invoke it during task execution.
Use Cases
This skill is perfect for sports analysts, data enthusiasts, and casual viewers who want instant insights into the sport. Typical use cases include comparing the throttle usage and speed traps of two drivers during a specific sector, monitoring weather changes during a race session, retrieving team radio clips, or calculating the gap between a leader and the chasing pack using interval data. It is particularly useful for retrospective race analysis, such as identifying when a specific pit strategy was deployed or why a driver's lap time dropped.
Example Prompts
- "Who won the last race, and what was the average stint length for the top three finishers?"
- "Compare Max Verstappen and Lando Norris's telemetry during the last qualifying session; specifically look at brake usage in turn 4."
- "Show me the team championship standings and list all team radio messages from the latest race."
Tips & Limitations
To maximize the reliability of the output, always aim to define the session context using --session. If you are unsure which session to query, use f1 sessions --meeting latest to retrieve the relevant session key first. Note that some data, such as telemetry, is extremely granular (3.7 Hz), so use the --filter flag to narrow down your results to prevent overwhelming the agent context window with thousands of lines of data. Be aware that the API relies on the availability of the OpenF1 platform, and certain real-time data may experience slight delays depending on the official timing feed.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-barronlroth-f1-cli": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: external-api, code-execution