What do I need to start?

You need a Rube MCP endpoint, an active API Sports connection via the api_sports toolkit, and access to RUBE_SEARCH_TOOLS.

Why must I always call RUBE_SEARCH_TOOLS first?

Tool schemas change over time; RUBE_SEARCH_TOOLS provides current slugs and required fields to avoid hardcoding.

What if tool slugs change between runs?

RUBE_SEARCH_TOOLS should be re-run to fetch updated slugs and schemas before executing tools.

api-sports-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/api-sports-automation --openclaw

Files (1)

SKILL.md

2.9 KB

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`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/api-sports-automation/SKILL.mdView on GitHub

Overview

This skill automates API Sports operations using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas first via RUBE_SEARCH_TOOLS and validating a live connection with RUBE_MANAGE_CONNECTIONS before running workflows. This approach keeps automations aligned with the latest API schemas.

How This Skill Works

First, ensure Rube MCP is connected and RUBE_SEARCH_TOOLS is available. Then discover tools for your API Sports task, verify the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tools with RUBE_MULTI_EXECUTE_TOOL, including the memory parameter.

When to Use It

Automating routine API Sports tasks (e.g., fetching stats) after discovering current tool schemas.
Setting up a new API Sports workflow by verifying a live connection and authenticating via RUBE_MANAGE_CONNECTIONS.
Running multi-tool sequences with RUBE_MULTI_EXECUTE_TOOL after obtaining tool slugs from RUBE_SEARCH_TOOLS.
Handling tool schema changes by re-running RUBE_SEARCH_TOOLS before each workflow to fetch updated fields.
Dealing with paginated API responses by using returned tokens and continuing fetches until complete.

Quick Start

Step 1: Discover available tools with RUBE_SEARCH_TOOLS using use_case: 'API Sports operations'.
Step 2: Check the API Sports connection with RUBE_MANAGE_CONNECTIONS and confirm the toolkit 'api_sports' is ACTIVE.
Step 3: Execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using memory: {} and a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and required fields.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from the search results; never hardcode slugs or args.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow; generate new ones for independent workflows.

Example Use Cases

Automate daily API Sports stats retrieval by discovering the relevant tool, validating the connection, then executing the stats tool with a fresh session.
Update lineup or roster data by discovering the appropriate tool, confirming ACTIVE connection, and chaining tools to push updates.
Perform bulk score updates across multiple events by discovering tool slugs and executing them in a single workflow with proper memory handling.
Generate a multimodal report by executing a sequence of tools that fetch data, transform it, and export a summary.
Handle a paginated games list by iteratively calling tools until all pages are fetched using the provided pagination tokens.

Frequently Asked Questions

Add this skill to your agents