api-sports-automation

通过 Rube MCP 自动化 API Sports 查询与数据处理，快速完成体育数据任务。

来源

GitHub

更新于

2026-06-07

// 安全评估低风险

仅提示词，不执行代码
开源可审计

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "api-sports-automation" 技能：
1. 下载 https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/api-sports-automation/SKILL.md
2. 保存为 ~/.claude/skills/api-sports-automation/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

查询今日比赛

输入

先搜索 API Sports 相关工具及当前 schema，再调用合适的接口，获取今天所有足球比赛的赛程，按联赛分组输出，包含开赛时间、主客队和比赛状态。

预期产出

一份按联赛整理的今日足球赛程列表，字段清晰、便于查看或继续处理。

统计球队近期战绩

输入

先搜索 API Sports 工具和 schema，然后查询指定球队最近 5 场比赛结果，统计胜平负、总进球和失球，并总结近期状态。

预期产出

包含最近 5 场明细、汇总统计和简短状态分析的结果。

生成联赛积分表

输入

先搜索当前可用的 API Sports 工具与 schema，再获取指定联赛本赛季积分榜，输出排名、球队、积分、胜平负和净胜球，并整理成表格。

预期产出

一张结构化的联赛积分表，可直接用于汇报、分析或后续自动化流程。

// 文档

API Sports Automation via Rube MCP

Automate API Sports operations through Composio's API Sports toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/api_sports

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active API Sports connection via RUBE_MANAGE_CONNECTIONS with toolkit api_sports
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit api_sports
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "API Sports operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific API Sports task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["api_sports"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with API Sports-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `api_sports`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`