home / skills / composiohq / awesome-claude-skills / api-sports-automation

api-sports-automation skill

safe

/api-sports-automation

This skill automates API Sports tasks via Rube MCP, always discovering current tool schemas before execution to ensure accurate, up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill api-sports-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: api-sports-automation
description: "Automate API Sports tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# 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](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `api_sports`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates API Sports operations through Composio's API Sports toolkit using Rube MCP. It guides discovery of available tools, manages connections, and runs schema-compliant executions to perform sports-data workflows reliably. The workflow emphasizes always searching tools first and verifying connection status before execution.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover current tool slugs and input schemas, RUBE_MANAGE_CONNECTIONS to ensure an active API Sports connection, and RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) to run the selected tools. It enforces schema compliance, session reuse, and inclusion of a memory parameter in multi-execute calls.

When to use it

Automating sports-data retrieval, stats aggregation, and schedule updates.
Running batch or bulk API Sports operations with Composio tools.
Building reproducible workflows that depend on up-to-date tool schemas.
Orchestrating multi-step tasks that require multiple composio tools in sequence.
When you need safe execution with connection checks and pagination handling.

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and full input schemas; do not hardcode tool names or fields.
Verify toolkit connection with RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE before running tools.
Send schema-compliant arguments exactly as returned by the search; mismatched field names or types will fail.
Include an explicit memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse the same session_id within a workflow; generate a new session for distinct workflows.
Check responses for pagination tokens and iterate until all pages are retrieved.

Example use cases

Fetch live fixtures and player stats for a league using discovered API Sports endpoints.
Bulk import historical match data via RUBE_REMOTE_WORKBENCH and run composio tool batches.
Create a daily workflow that checks connection, pulls new events, and updates downstream systems.
Perform multi-tool workflows: discover tools, validate schema, then execute data enrichment and storage steps.
Run pagination-safe exports of team and player datasets for analytics pipelines.

FAQ

What is the first call I should make?

Always call RUBE_SEARCH_TOOLS with an API Sports use case to get current tool slugs and input schemas.

What if RUBE_MANAGE_CONNECTIONS shows NOT ACTIVE?

Follow the returned authentication link to complete setup, then re-check until the connection status is ACTIVE before executing tools.