Name: recurly
Rating: 60.8 (1 reviews)
Author: membranedev

recurly

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

82%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 a tight, executable guide to driving Recurly through the Membrane CLI, with concrete commands and a state-driven connection workflow including validation. Its main gaps are inconsistent step numbering and a couple of spots where auth-plumbing prose could be trimmed.

Suggestions

Fix the step numbering: relabel the polling section as a proper numbered step and define the referenced 'Step 2' (searching/running actions) so the 'skip to Step 2' cues resolve.

Trim the explanatory asides about Membrane handling auth, since the Best Practices section already states the credential lifecycle.

Consider moving the proxy request options table into a separate reference file to keep the main flow lean, since the body already exceeds a simple overview.

Dimension	Reasoning	Score
Conciseness	The body is an efficient command reference that assumes Claude's competence, with only minor over-explanation (e.g. 'so you can focus on the integration logic rather than auth plumbing').	4 / 5
Actionability	It provides fully executable, copy-paste-ready bash commands across install, auth, connection, action search/run, and proxy requests, plus a concrete options table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state-based validation checkpoints and feedback loops (polling READY/BUILDING/CLIENT_ACTION_REQUIRED), but inconsistent numbering ('1b' with no '1a', 'skip to Step 2' with no labeled Step 2) slightly mars the sequence.	4 / 5
Progressive Disclosure	There are no bundle files; the single SKILL.md is well-organized into clear sections with one external docs link, though content like the proxy options table could arguably live in a reference file.	4 / 5
	Total	17 / 20 Passed

Description

61%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 cleanly answers both what the skill does and when to use it, anchored to a distinct brand. Its weakness is that the capability verbs are generic and the trigger terms lean on the brand name rather than the natural subscription/billing vocabulary users would say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Recurly actions such as 'manage subscriptions, billing info, invoices, plans, and coupons'.

Add natural trigger terms a user would actually say, e.g. 'Use when the user wants to manage Recurly subscriptions, billing, invoices, or plans.'

Reference the key Recurly objects (Account, Subscription, Invoice, Plan, Coupon) to make the scope concrete and further distinguish the skill.

Dimension	Reasoning	Score
Specificity	It names the Recurly domain but the actions ('Manage data, records, and automate workflows') are generic rather than concrete, sitting just below the anchor that names 1-2 concrete actions.	2 / 5
Completeness	Both a 'what' (Recurly integration, manage data/records/workflows) and a 'when' ('Use when the user wants to interact with Recurly data') are present, though the trigger is somewhat generic.	4 / 5
Trigger Term Quality	It surfaces the brand name 'Recurly' and 'Recurly data' but omits the natural terms users say (subscriptions, billing, invoices, plans), missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	The named Recurly brand carves a clear niche with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	14 / 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/recurly/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.