Name: rapidapi
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

rapidapi

RapidAPI integration. Manage data, records, and automate workflows. Use when the user wants to interact with RapidAPI data.

Quality

66%

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/rapidapi/SKILL.md

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 highly actionable with executable commands and a clear connection-state feedback loop, weakened only by an unnecessary introductory concept explanation and slightly loose step numbering. It is well-organized and self-contained.

Suggestions

Cut the opening "RapidAPI is a marketplace..." paragraph and the "RapidAPI Overview" tree; assume Claude knows what RapidAPI is and lead with the workflow.

Fix the step numbering: label the connection step "1," remove the orphaned "1b," and explicitly label the referenced "Step 2" (searching/running actions).

Move the proxy flags table into a short reference section or keep it but trim the surrounding prose to tighten token use.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but the opening paragraph explains what RapidAPI is ("RapidAPI is a marketplace where developers can find, test, and connect to thousands of APIs...") and includes minor fluff like "so you can focus on the integration logic rather than auth plumbing" — concepts Claude already knows.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case — install, login, connection ensure, polling, action list/run with JSON input, and proxy requests — plus a concrete flags table, fully covering the typical workflow.	5 / 5
Workflow Clarity	The connect → poll → search → run sequence has explicit state checkpoints and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the "Step 2" reference is unlabeled and a "1b" step appears without a corresponding "1," leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	Content is organized into clear sections (Overview, Working with RapidAPI, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nesting and easy navigation; at ~160 lines with no external references it is well-structured but does not qualify for the sub-50-line clean 5.	4 / 5
	Total	16 / 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 trigger and a clear RapidAPI niche, but its action language is generic and its keyword coverage lacks synonyms. Tightening the capability list and adding common user phrases would lift it from mid-range to strong.

Suggestions

Replace generic verbs with concrete RapidAPI actions, e.g., "Discover, test, and connect to APIs; manage subscriptions and usage."

Add natural trigger synonyms users say, such as "find APIs," "test APIs," "API marketplace," or "API subscriptions."

Keep the explicit "Use when..." clause but expand the trigger to cover the common intents (searching for, testing, or integrating APIs).

Dimension	Reasoning	Score
Specificity	The description names the domain ("RapidAPI integration") but the actions listed — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete, matching the anchor for naming the domain with minimal/generic actions.	2 / 5
Completeness	It has both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when..." trigger clause; the when is clear but the what is vague rather than concrete, so it does not reach the explicit-concrete anchor of 5.	4 / 5
Trigger Term Quality	It includes the natural term "RapidAPI" and the phrase "interact with RapidAPI data," but misses common variations and synonyms a user might say (e.g., find/test APIs, API marketplace, subscriptions), so keyword coverage is partial.	3 / 5
Distinctiveness Conflict Risk	"RapidAPI integration" carves a clear niche with a distinct trigger, but the generic "Manage data, records, and automate workflows" phrasing leaves minor overlap risk with other data/API 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/rapidapi/SKILL.md
Commit: f484c82

Reviewed: 5 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.