Name: rapyd
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

rapyd

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

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/rapyd/SKILL.md

Quality

Content

81%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 body is highly actionable with executable commands, a well-sequenced connection workflow including polling/validation checkpoints, and clean section organization. The chief weakness is conciseness: the intro paragraph, an auth-plumbing aside, and a rambling agent-types note add tokens Claude doesn't need.

Suggestions

Trim the opening Rapyd overview paragraph and the "so you can focus on the integration logic rather than auth plumbing" aside to assumed knowledge.

Rewrite the agent-types line into a concise list (e.g. "claude, openclaw, codex, warp, windsurf") and fix the stray colon/wording.

Consider moving the entity list and/or proxy flag table into a references/ file and linking from the overview to push the skill toward one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands throughout, but includes some unnecessary padding — the opening paragraph on what Rapyd is, "so you can focus on the integration logic rather than auth plumbing", and a slightly rambling/typo-ridden agent-types note — fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Provides fully executable, copy-paste-ready bash commands for every stage (install, login, connection ensure/get with --wait, action list/run, request) plus a concrete flag table for proxying, covering the common cases.	5 / 5
Workflow Clarity	Clear install -> auth -> connect -> wait -> search -> run sequence with explicit validation checkpoints and a feedback loop (poll while BUILDING, branch on CLIENT_ACTION_REQUIRED, re-poll after the user acts), matching the explicit-validation anchor.	5 / 5
Progressive Disclosure	Well-organized into clear single-level sections with no nested file references, but it is a monolithic ~155-line SKILL.md with no bundle files, so structure is good rather than the ideal clear-overview-pointing-to-one-level-deep-references arrangement.	4 / 5
	Total	17 / 20 Passed

Description

66%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 well-structured with both a what and a when clause and a distinct, low-conflict trigger via the Rapyd proper noun. Its main weakness is generality: the listed actions ("manage data, records, automate workflows") and the trigger phrase ("interact with Rapyd data") are vague and omit the natural payment-domain terms users would actually say.

Suggestions

Replace generic actions with concrete Rapyd operations, e.g. "Create customers, process payments, issue refunds, manage wallets and payouts, and handle disputes".

Add concrete trigger phrases a user would naturally say, e.g. "Use when the user wants to process Rapyd payments, manage Rapyd customers or wallets, issue refunds, or call the Rapyd API".

Include common synonyms/file or endpoint references where applicable (e.g. "Rapyd API", "Rapyd payment") to broaden natural-language triggering.

Dimension	Reasoning	Score
Specificity	Names the Rapyd domain and a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic ("manage data", "records") rather than several specific concrete operations, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	Explicitly answers both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Rapyd data"), but the "when" clause is generic rather than concrete, matching the both-present-but-when-could-be-more-specific anchor rather than the missing-when level 3 or the concrete-triggers level 5.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Rapyd", "data", "records", "workflows") but misses the natural payment-specific phrases a user would say ("Rapyd payments", "Rapyd API", "create customer", "refund") and common synonyms, fitting the some-relevant-keywords anchor.	3 / 5
Distinctiveness Conflict Risk	The proper noun "Rapyd" paired with "Rapyd integration" / "interact with Rapyd data" carves out a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/rapyd/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.