Name: chargebee
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

chargebee

Chargebee integration. Manage Customers. Use when the user wants to interact with Chargebee data.

Quality

69%

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

Quality

Content

72%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 workflow, but it inlines a large actions table that belongs in a separate reference file and omits validation steps for destructive operations. Splitting reference material out and adding confirmation/verification for destructive actions would raise the weaker dimensions.

Suggestions

Move the Popular actions table and proxy flags into a separate reference file (e.g., references/actions.md) and link to it from SKILL.md to improve progressive disclosure.

Add explicit confirmation/verification steps before running destructive actions such as Delete Customer, Cancel Subscription, Refund Invoice, and Void Invoice.

Trim the introductory paragraph describing what Chargebee is, since it explains background Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands and a reference table, with only minor over-explanation (the introductory paragraph describing what Chargebee is and some explanatory prose).	4 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a full popular-actions table with keys and a proxy flags table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is well sequenced with state-check checkpoints and a polling feedback loop, but destructive/batch actions (Delete Customer, Cancel/Refund/Void) lack any verification or confirmation steps, capping this dimension at 3.	3 / 5
Progressive Disclosure	The file is well sectioned but runs ~160 lines with the 20-row Popular actions table and proxy options inlined, and there are no external reference files (references/, scripts/, assets/ are absent), so bulk reference material that should be separate is inline.	3 / 5
	Total	15 / 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 answers both what and when and targets a clearly distinct platform niche, but it is light on concrete actions and natural trigger terms. Expanding the action list and trigger keywords would lift specificity and trigger_term_quality.

Suggestions

List more concrete actions beyond "Manage Customers" (e.g., create and manage subscriptions, invoices, plans, and refunds) to improve specificity.

Add natural trigger phrases users would say, such as subscriptions, billing, invoices, or recurring payments, to broaden trigger-term coverage.

Tighten the when-clause to name concrete intents (e.g., "Use when the user wants to manage Chargebee subscriptions, customers, or invoices") rather than the generic "interact with Chargebee data".

Dimension	Reasoning	Score
Specificity	The description names the domain (Chargebee) and one concrete action ("Manage Customers"), but coverage is not comprehensive and "interact with Chargebee data" is generic.	3 / 5
Completeness	Both "what" ("Chargebee integration. Manage Customers.") and "when" ("Use when the user wants to interact with Chargebee data.") are explicitly present, though the when-clause is generic rather than listing concrete triggers.	4 / 5
Trigger Term Quality	"Chargebee" and "Customers" are relevant natural keywords, but common variations users would say (subscriptions, invoices, billing, payments) are missing.	3 / 5
Distinctiveness Conflict Risk	"Chargebee" is a specific named platform giving 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/chargebee/SKILL.md
Commit: f484c82

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