Name: chargeblast
Rating: 55.2 (1 reviews)
Author: membranedev

chargeblast

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

Quality

63%

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

Quality

Content

63%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 body delivers strong executable guidance and a clear connection workflow with state-based checkpoints, but is weighed down by apologetic fluff and keeps all reference material inline rather than splitting it out.

Suggestions

Remove the "Official docs: I am sorry, I cannot provide..." line and the Stripe/Braintree comparison; keep only actionable content.

Fix the dangling "skip to Step 2" reference by labeling the action-search/run sections as explicit numbered steps.

Move the Popular actions table and proxy flag reference into a separate reference file referenced one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but padded lines like "Think of it as a Stripe or Braintree alternative" and the apologetic "Official docs: I am sorry, I cannot provide the API documentation URL..." add noise.	3 / 5
Actionability	Provides executable commands throughout (install, login, connection ensure, action list/run, request) plus a Popular actions table; minor gaps remain with placeholders like CONNECTION_ID and <actionId>.	4 / 5
Workflow Clarity	Clear install→auth→connect→poll→search→run sequence with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling feedback loops; the dangling "skip to Step 2" reference is a minor gap.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inlined into a ~155-line SKILL.md; section structure is reasonable but the Popular actions and proxy options tables could live in separate reference files.	3 / 5
	Total	14 / 20 Passed

Description

62%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 covers both what the skill does and when to use it with a clear named-app trigger, but relies on generic action language and weak trigger phrasing rather than concrete capabilities.

Suggestions

Replace generic verbs with concrete actions, e.g. "Manage Chargeblast merchants, descriptors, orders, alerts, and credit requests".

Expand the trigger to list natural user phrases, e.g. "Use when the user wants to manage Chargeblast merchants, enroll/dispute alerts, or upload orders".

Mention specific Chargeblast concepts (merchants, descriptors, alerts, disputes) so the trigger is unmistakable.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Chargeblast domain and a few actions, but the actions are generic rather than concrete; not comprehensive enough for a 4.	3 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Chargeblast data") are present, though the 'when' could be more specific.	4 / 5
Trigger Term Quality	The trigger phrase "interact with Chargeblast data" provides some relevant keywords but lacks natural synonyms or variations a user would actually say.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Chargeblast app gives a distinct niche with low conflict risk, but the generic action verbs leave minor overlap potential with other data skills.	4 / 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/chargeblast/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.