api-sports-automation
Automate API Sports tasks via Rube MCP (Composio). Always search tools first for current schemas.
87
Quality
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently communicates how to use API Sports via Rube MCP. The workflow is clear with appropriate validation checkpoints, and the content respects token budget. The main weakness is that the tool call examples use a pseudocode format rather than showing actual executable syntax, which slightly reduces actionability.
Suggestions
Clarify the exact syntax for tool calls - are these function calls, JSON payloads, or MCP protocol messages? Show the actual format Claude should output.
Add a concrete end-to-end example showing a real API Sports task (e.g., fetching football match data) with actual tool slugs and response handling.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts. Every section serves a purpose with no padding or unnecessary context about what APIs or sports data are. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameters, but the examples are pseudocode-like representations rather than actual executable code. The argument placeholders and comments reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status and explicit instruction to confirm ACTIVE status before proceeding. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Quick reference table aids navigation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- ComposioHQ/awesome-claude-skills
- Commit
2790447
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.