CtrlK
BlogDocsLog inGet started
Tessl Logo

api-sports-automation

Automate API Sports tasks via Rube MCP (Composio). Always search tools first for current schemas.

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/api-sports-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured, actionable, and assumes Claude's intelligence, with clear workflows and validation checkpoints. Minor redundancy and placeholder arguments are the main areas for tightening.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, though the 'search first' guidance is repeated across Prerequisites, Tool Discovery, and Known Pitfalls, adding minor redundancy.

4 / 5

Actionability

Concrete MCP call blocks (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) show real parameter structure, but use placeholders like 'your_session_id' and 'TOOL_SLUG_FROM_SEARCH'.

4 / 5

Workflow Clarity

A clear three-step sequence (discover, check connection, execute) includes validation checkpoints (confirm ACTIVE before running, pagination continuation), with only minor gaps in post-execute error handling.

4 / 5

Progressive Disclosure

A single self-contained file with well-organized sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference) and no nested references; slight cross-section redundancy keeps it just below ideal.

4 / 5

Total

16

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is clear about the domain and core behavior but lacks an explicit use-when trigger and relies on fairly narrow keywords. It is distinct but would benefit from explicit activation guidance.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks to automate or query API Sports data (fixtures, scores, player stats) via Rube MCP.'

Broaden trigger terms with natural synonyms and concrete use cases such as 'sports data, fixtures, live scores, player statistics, team info'.

Replace the generic 'Automate API Sports tasks' with specific actions like 'fetch fixtures, scores, standings, and player stats'.

DimensionReasoningScore

Specificity

"Automate API Sports tasks via Rube MCP (Composio)" names the domain and a concrete action ("Always search tools first for current schemas"), but the main verb "Automate ... tasks" is generic and not comprehensive.

3 / 5

Completeness

It clearly states what the skill does, but provides no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

It includes relevant keywords ("API Sports tasks", "Rube MCP", "Composio") that a user might say, but offers few natural variations or synonyms beyond the literal toolkit name.

3 / 5

Distinctiveness Conflict Risk

"API Sports" scoped to "Rube MCP (Composio)" carves a clear niche with mostly distinct triggers, though it could overlap with sibling Composio/Rube toolkit skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
ComposioHQ/awesome-claude-skills
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.