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

Blog Docs Log in Get started

recharge

ReCharge integration. Manage Customers. Use when the user wants to interact with ReCharge 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/recharge/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 solid connection-state workflow, weakened mainly by light over-explanation and a broken step-numbering scheme. No bundle files are present, so progressive disclosure rests on the in-file structure alone.

Suggestions

Trim assumed-knowledge framing: drop the "ReCharge is a subscription management platform..." intro and the "so you can focus on the integration logic rather than auth plumbing" commentary.

Fix the dangling cross-reference: either label the action-search/run section "Step 2" or remove the "skip to Step 2" / "1b" numbering so the flow reads cleanly top-to-bottom.

Consider moving the proxy flag table and action-discovery details into a references/ file linked from the body, giving the overview a cleaner one-level-deep structure.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command reference, but includes unnecessary explanation Claude already knows (the opening "ReCharge is a subscription management platform..." sentence and "so you can focus on the integration logic rather than auth plumbing" padding).	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, poll-for-ready, action list/run, proxy) plus a complete flag table, fully executable with standard placeholders.	5 / 5
Workflow Clarity	The connection flow has a clear state machine with an explicit poll-until-READY checkpoint and error-recovery branches (CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but the prose references a "Step 2" that is never labeled and a "1b" section with no 1a, leaving minor navigation gaps.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no nested references, but everything is inlined in one file with no one-level-deep reference split, which is acceptable here though not ideal for a 140-line doc.	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 correctly pairs a what statement with an explicit Use-when trigger and anchors on a distinctive platform name, but it is thin on concrete actions and natural synonyms. Expanding the action list and trigger terms would lift the weaker dimensions.

Suggestions

Replace the single generic verb "Manage Customers" with several concrete actions, e.g. "Create and update subscriptions, manage charges, and look up customer addresses in ReCharge."

Broaden the trigger clause with natural synonyms: "Use when the user wants to manage ReCharge subscriptions, recurring billing, charges, or customer data."

Keep the third-person imperative style but ensure at least 2-3 specific actions so specificity reaches the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	"Manage Customers" names the ReCharge domain but offers only one generic action verb ("Manage"), matching the anchor where actions are minimal or generic rather than multiple concrete actions.	2 / 5
Completeness	It states both the what ("ReCharge integration. Manage Customers.") and an explicit when ("Use when the user wants to interact with ReCharge data"), though the when clause is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces the core trigger "ReCharge" plus "Customers" and "ReCharge data", but omits common variations a user might say such as subscriptions, recurring billing, or charges.	3 / 5
Distinctiveness Conflict Risk	The named platform "ReCharge" gives it a clear niche with minimal conflict risk, but the generic "Manage Customers" phrasing leaves minor overlap with general customer-management 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/recharge/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.