$ ~/registry/skill/composiohq-composio-skills-api-sports-automation

SKILL

api-sports-automation

Name: api-sports-automation
Author: Composio

Automate API Sports queries and data workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill appears to be prompt/documentation content from an open-source, widely adopted repository, with no direct local secret requirement or local execution steps, so the overall risk is relatively low. However, it is designed to rely on external Rube MCP and follow-on third-party connection authorization, which introduces network egress and account-consent considerations that should be verified before use.

CredentialsCaution

The material says 'No API keys needed,' but it also requires establishing an ACTIVE `api_sports` connection via `RUBE_MANAGE_CONNECTIONS` and following a returned auth link. This suggests credentials are handled in an external connection flow rather than being truly unnecessary; that creates normal third-party account authorization/token grant exposure, but there is no explicit sign of credential theft in the provided material.

Network egressCaution

The README explicitly requires connecting to the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to search tools, manage connections, and execute API Sports actions, so user requests and related parameters will be sent to the stated third-party service. The endpoint is identified and functionally relevant, making this normal network behavior for this type of tool; no red flag indicates exfiltration to unrelated or unknown destinations.

Code executionLow risk

The system marks it as `prompt-only`, and the content is mainly instructions and call sequencing. It does not ask the user to download, install, or run local scripts, nor does it claim local shell/process privileges. Based on the provided material, there is no direct local code execution capability.

Data accessCaution

The skill itself does not claim local file read/write or local resource access, but it does perform operations through Rube/Composio against an external API Sports connection and maintains workflow state such as `session_id` and `memory`. The visible data access appears to be mainly within the remote toolchain and the linked external account; the exact permission boundary is not fully described and should be verified with least-privilege principles.

Supply chainLow risk

The source is an open GitHub repository with very strong community adoption (about 64.9k stars), which materially lowers supply-chain risk; the current artifact also appears to be documentation/skill content rather than an executable package. Although the license is unspecified and maintenance status is unknown, and the linked Rube/Composio services should still be reviewed, the available facts do not justify a high-risk rating.

Recommendations

Before enabling it, verify the privacy policy, data retention, and actual call scope of `rube.app/mcp` and Composio.
When authorizing `api_sports`, grant only the minimum permissions needed and periodically review/revoke unused connections.
Do not include unnecessary sensitive data in tool discovery or execution parameters; minimize inputs where possible.
For higher assurance, further review the actual implementation, logging practices, and permission model of Rube MCP and the related toolkit.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "api-sports-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/api-sports-automation/SKILL.md
2. Save it as ~/.claude/skills/api-sports-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate API Labz tasks via Rube MCP using current tool schemas.

ComposioGet→

$ loading_