Name: api-sports
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

api-sports

API Sports integration. Manage Sports. Use when the user wants to interact with API Sports data.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/api-sports/SKILL.md

Quality

Content

63%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 highly actionable with executable CLI commands and a clear, well-branched connection workflow, but it carries trimmable marketing prose and inlines bulk reference tables that would be better split into reference files. Step numbering also needs fixing.

Suggestions

Remove the marketing-style overview paragraph ("API Sports provides... used by sports websites, mobile apps..."); keep only what Claude needs to drive the CLI.

Move the 20-row Popular actions table and the proxy flag table into a references/ file (e.g. ACTIONS.md) and link to it from the body, so SKILL.md stays an overview.

Fix the workflow numbering: label the connection step "1a", the wait/poll step "1b", and explicitly label "Step 2" as the Searching-for-actions section that "skip to Step 2" points to.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but the marketing intro ("API Sports provides real-time sports data... used by sports websites, mobile apps, and fantasy sports platforms...") is padding Claude does not need, and the 20-row actions table inflates tokens.	3 / 5
Actionability	Copy-paste-ready commands (install, login, connection ensure, action list/run, request) with flag tables and a 20-action catalog provide mostly executable guidance, with minor gaps around placeholders like CONNECTION_ID, actionId, and --intent "QUERY".	4 / 5
Workflow Clarity	A clear install→login→connect→poll→state-branch→search→run sequence exists with a poll/user-act/re-poll feedback loop and error-field handling, but step numbering is broken ("skip to Step 2" with no Step 2 label, "1b" without a "1a").	4 / 5
Progressive Disclosure	The skill is a single ~175-line file with good section headings, but bulk reference material (the 20-row actions table and proxy flag table) is inlined with no offloading to reference files and no signaled one-level-deep references.	3 / 5
	Total	14 / 20 Passed

Description

57%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 answers both what and when with an explicit Use-when clause and names a distinct service, but its actions are generic and its trigger terms lack the natural synonyms users would actually say. It is competent but not comprehensive.

Suggestions

Replace the generic "Manage Sports" with concrete actions, e.g. "Get leagues, fixtures, standings, players, and team statistics from API Sports."

Expand the Use-when clause with natural trigger phrases users say, e.g. "Use when the user asks for sports fixtures, league standings, scores, player stats, or live odds."

Add common synonyms/keywords (fixtures, matches, standings, tables, scores, statistics) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Phrases "Manage Sports" and "interact with API Sports data" name the domain but use minimal, generic actions rather than concrete verbs like get fixtures/standings/players.	2 / 5
Completeness	Both a "what" ("API Sports integration. Manage Sports.") and an explicit "when" ("Use when the user wants to interact with API Sports data") are present, though the when-clause is generic rather than listing concrete triggers.	4 / 5
Trigger Term Quality	Keywords "API Sports", "Sports", and "interact with API Sports data" are relevant but miss common natural variations users would say (fixtures, standings, scores, statistics).	3 / 5
Distinctiveness Conflict Risk	"API Sports" names a specific service giving a clear niche, but the broad "Manage Sports" trigger leaves minor overlap risk with other sports-related skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/api-sports/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.