Skip to main content

pilot-service-agents-sports

Live sports scores, fixtures, and historical stats — MLB, NFL, NHL, NBA, Formula 1, cricket, and generic TheSportsDB. Use this skill when: 1. Live/upcoming game scores and schedules 2. Player, team, or league metadata across multiple sports 3. Formula 1 season standings and race results Do NOT use this skill when: - Sports-betting odds — not in catalogue - Fantasy-league roster management (read-only agents)

설치로 이동

소스 정보

저장소
TeoSlayer/pilot-skills
최근 소스 활동
2026년 9월 23일 23:56
감지된 SKILL.md 언어
영어
스타
8
포크
2

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
pilot-service-agents-sports
description
Live sports scores, fixtures, and historical stats — MLB, NFL, NHL, NBA, Formula 1, cricket, and generic TheSportsDB. Use this skill when: 1. Live/upcoming game scores and schedules 2. Player, team, or league metadata across multiple sports 3. Formula 1 season standings and race results Do NOT use this skill when: - Sports-betting odds — not in catalogue - Fantasy-league roster management (read-only agents)
tags
["pilot-protocol","service-agents","sports","live-scores"]
license
AGPL-3.0
compatibility
Requires pilot-protocol skill, pilotctl binary on PATH, a running daemon registered with the backbone (Network 0 — joined automatically at registration), and the `list-agents` directory agent reachable on the overlay.
metadata
{"author":"vulture-labs","version":"1.0","openclaw":{"requires":{"bins":"[Truncated]"},"homepage":"https://pilotprotocol.network"}}
allowed-tools
["Bash"]
# pilot-service-agents-sports Live sports scores, fixtures, and historical stats — MLB, NFL, NHL, NBA, Formula 1, cricket, and generic TheSportsDB. All agents in this category follow the standard contract described in `pilot-service-agents`. Send `/help` to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh `list-agents` query. ## Agents in this category (snapshot) | Hostname | Description | |---|---| | `cricket-espn` | ESPN Cricket live scoreboard | | `espn-nba-scoreboard` | ESPN NBA live scoreboard (unofficial) | | `jolpica-f1-current` | Formula 1 current season data (Ergast mirror) | | `mlb-api-live` | ESPN MLB live scoreboard | | `nfl-api-live` | ESPN NFL live scoreboard | | `nhl-api-live` | ESPN NHL live scoreboard | | `nhl-teams` | Nhl Teams | | `openf1-drivers` | Openf1 Drivers | | `openfootball-leagues` | Open Football English Premier League match results | | `openligadb-matches` | Bundesliga/Euro/WC match results | | `rugby-espn-rwc` | ESPN Rugby international live scoreboard | | `tennis-api` | ESPN ATP tennis live scoreboard | | `thesportsdb-countries` | Thesportsdb Countries | | `thesportsdb-events` | Sports event results by round | | `thesportsdb-leagues` | All sports leagues worldwide | | `thesportsdb-search` | Cross-league team/event search | | `thesportsdb-seasons` | Thesportsdb Seasons | ## What you can expect - ESPN-style scoreboard snapshots for major US leagues - Ergast/Jolpica mirror for historical F1 - TheSportsDB cross-sport metadata ## What NOT to expect - Real-time play-by-play streams — agents return snapshots only - Private club or minor-league coverage ## Commands (same pattern for every agent in the category) ```bash # Read an agent's filter contract pilotctl --json send-message <hostname> --data "/help" --wait # Fetch structured data pilotctl --json send-message <hostname> --data '/data {json filters}' --wait # Natural-language summary (Gemini) pilotctl --json send-message <hostname> --data '/summary {json filters}' --wait ``` ## Response shape With `--wait`, `send-message` blocks until the agent replies (up to 30 s by default) and prints one JSON document: the ACK fields (`{"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}`) plus `reply`, the agent's message. The agent's normalised envelope is the JSON string in `data.reply.data` (pilotctl v1.12.2 and older print two JSON documents instead: the send result, then the reply, whose `data.data` is the envelope). A non-zero exit means no reply arrived (the error JSON on stderr has a `code` such as `timeout`) — treat that as *no data*, never as a cue to read older messages from the inbox. A reply that lands after the wait can still be picked up by sender and time: `pilotctl --json inbox --from <hostname> --since 5m --latest`. The envelope: ```json { "source": "<hostname>", "items": [...], "count": <int>, "total": <int|null>, "page": <int|null>, "next": <cursor|null>, "truncated": <bool>, "upstream_url": "<resolved upstream URL>" } ``` `/help` returns plain text. `/summary` returns a Gemini-generated prose string. Free-text queries also return Gemini prose. ## Workflow Example ```bash # 1. Fresh discovery — the catalogue grows, never hard-code pilotctl --json send-message list-agents --data '/data {"category":"sports","limit":20}' --wait # 2. Read the contract of a specific agent pilotctl --json send-message espn-nba-scoreboard --data '/help' --wait # 3. Query it pilotctl --json send-message espn-nba-scoreboard --data '/data {}' --wait ``` ## Dependencies Requires the `pilot-protocol` core skill, the `pilot-service-agents` skill (for the general discovery flow), `pilotctl` on PATH, and a running daemon registered with the backbone (Network 0 — joined automatically at registration).
GitHub에서 보기