Name: ratepay
Rating: 52.8 (1 reviews)
Author: membranedev

ratepay

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

Quality

59%

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

Quality

Content

61%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 concrete CLI commands and a well-structured connection workflow, but it is held back by padding, broken step numbering, and missing verification guidance for destructive operations. No external references are used, which is appropriate for its size.

Suggestions

Add a verification/checkpoint step after running actions or proxy requests (e.g. inspect the `output`/error field before proceeding), especially for refunds and other destructive calls.

Fix the workflow numbering: relabel "1b" as part of a clear "1. Ensure connection" / "2. Discover and run actions" sequence so "skip to Step 2" resolves.

Trim the introductory Ratepay paragraph and the "auth plumbing" commentary to reduce tokens, keeping only what Claude does not already know.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but includes unnecessary padding such as the Ratepay intro paragraph, the "auth plumbing" commentary, and a thin overview bullet list that could be trimmed.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands cover install, auth, connection, action discovery/execution, and proxying, with a flag table; the gap is that no concrete Ratepay-specific action example is given, relying on discovery with placeholders.	4 / 5
Workflow Clarity	The connection flow has clear state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again loop, but numbering is broken ("skip to Step 2" with no Step 2; "1b" with no "1a") and destructive operations like refunds lack verification steps.	3 / 5
Progressive Disclosure	No bundle files exist; the skill is a self-contained, well-organized SKILL.md with clear section headers and easy navigation, though some inline content (the clientAction detail, the proxy flag table) could be split into references.	4 / 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 correctly names the niche and provides an explicit use-when clause, but relies on generic action language and a thin set of trigger terms. Tightening the actions to concrete Ratepay operations and adding natural trigger phrases would raise it.

Suggestions

Replace generic verbs with concrete Ratepay actions, e.g. "Create payment requests, manage refund and installment schedules, and configure merchant settings."

Expand trigger terms to include natural user phrases like "Ratepay payments, invoices, installment plans, or refunds".

Make the use-when clause more specific, e.g. "Use when the user wants to process payments, issue refunds, or manage Ratepay merchant configurations."

Dimension	Reasoning	Score
Specificity	It names the Ratepay domain but the actions ("Manage data, records, and automate workflows") are generic rather than concrete Ratepay-specific operations, matching the "names the domain but actions are minimal or generic" anchor.	2 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and an explicit "when" clause ("Use when the user wants to interact with Ratepay data") are present, but the trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	"Ratepay" and "interact with Ratepay data" are real natural keywords, but coverage is limited to the platform name with no variations (payment, invoice, installment) a user might actually say.	3 / 5
Distinctiveness Conflict Risk	Ratepay is a distinct named niche platform, giving minimal conflict risk, though the generic action phrasing ("manage data, records") creates minor overlap with other data-handling 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/ratepay/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.