Name: chargify
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

chargify

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

Quality

61%

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

Quality

Content

65%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 actionable and reasonably concise with strong command examples and a clear connection workflow, but it lacks validation checkpoints for destructive operations and keeps a large action catalog inline rather than splitting it into a reference file.

Suggestions

Add explicit validation/confirmation steps before destructive actions like delete-customer and cancel-subscription (e.g. fetch-then-confirm-then-run, or verify the returned state).

Move the 19-row Popular actions table into a separate references file (e.g. references/actions.md) and link to it from the body to improve progressive disclosure.

Trim the opening explanatory paragraph about what Chargify is, since Claude can infer it from the domain, and remove redundant asides like 'This is the fastest way to get a connection'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands, tables, and minimal preamble, but the opening paragraph explaining what Chargify is and a few explanatory asides ('This is the fastest way to get a connection...') could be trimmed, matching 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands for connection, action search, action run, and proxy requests with flag tables, but uses placeholders like <actionId> and does not show a fully parameterized destructive call, leaving minor gaps below a clean 5.	4 / 5
Workflow Clarity	The connection flow is well sequenced with state-based branching and polling feedback, but destructive and batch operations (Delete Customer, Cancel Subscription, Update Subscription) have no validation or confirmation checkpoints, triggering the destructive-operation cap of 3.	3 / 5
Progressive Disclosure	The body is well sectioned with clear headers but is a single ~160-line file with an inlined catalog of 19 actions that could be a separate reference; with no bundle references at all, it matches 'some structure but content that should be separate is inline'.	3 / 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 identifies the Chargify niche and includes a 'Use when' trigger, but its capabilities and trigger terms are generic rather than naming concrete Chargify concepts like subscriptions, billing, or invoices.

Suggestions

Replace generic verbs with concrete Chargify actions, e.g. 'Manage subscriptions, customers, invoices, and coupons in Chargify'.

Add natural user trigger phrases such as 'subscriptions', 'billing', 'recurring revenue', or 'invoices' alongside 'Chargify data'.

Tighten the 'when' clause to concrete triggers, e.g. 'Use when the user wants to manage Chargify subscriptions, customers, or billing'.

Dimension	Reasoning	Score
Specificity	The description names the Chargify domain but the actions are generic ('Manage data, records, and automate workflows') rather than concrete Chargify operations like subscriptions, billing, or invoices, matching the 'names domain but actions minimal or generic' anchor and falling short of naming concrete actions.	2 / 5
Completeness	It provides both a 'what' ('Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with Chargify data'), but the trigger phrase is generic rather than concrete, so it does not reach the explicit concrete-trigger level of 5.	4 / 5
Trigger Term Quality	'Chargify' is a strong domain keyword, but the remaining terms ('data', 'records', 'workflows') are generic and miss the natural user phrases like subscriptions, billing, invoices, or customers, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming a specific app ('Chargify integration') gives it a clear niche with minimal conflict risk, though the generic trigger words ('data') leave minor overlap risk versus a fully concrete-trigger description.	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/chargify/SKILL.md
Commit: f484c82

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