CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chargeblast

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/chargeblast/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 Membrane integration workflow is genuinely actionable — concrete CLI commands, a sensible connection state machine, and a useful proxy fallback — but the body is marred by a pasted-in model refusal ('I am sorry, I cannot provide the API documentation URL...'), broken internal step references ('skip to Step 2' with no Step 2; '1b' without '1a'), and an overview section (Customer/Charge/Plan/Invoice) that contradicts the actual action catalog (merchants, orders, alerts, disputes). No verification guidance exists for the destructive/batch actions the skill exposes.

Suggestions

Remove the generation artifact ('I am sorry, I cannot provide the API documentation URL for "Chargeblast"...') and the empty 'Chargeblast Overview' bullet list, which lists objects (Customer, Charge, Plan, Invoice) inconsistent with the real actions (merchants, orders, alerts).

Fix the broken workflow numbering: define the referenced 'Step 2', rename '1b' to match its parent step, and number the whole connect → poll → act sequence consistently.

Add a validation checkpoint before consequential actions, e.g. verify state with 'get-alert' or 'list-orders' output before 'unenroll-merchant' or 'update-alert', and confirm results after 'upload-orders' batch uploads.

DimensionReasoningScore

Conciseness

The CLI instructions are mostly efficient, but there is unnecessary padding: 'Think of it as a Stripe or Braintree alternative', a leftover generation artifact ('I am sorry, I cannot provide the API documentation URL... because it is not a widely known or documented application.'), the empty 'Chargeblast Overview' bullets ending in the filler line 'Use action names and parameters as needed.', and inconsistent install commands ('npm install -g @membranehq/cli@latest' vs 'npx @membranehq/cli'). Fits 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not a 4 because the apology line and filler overview are clearly trimmable waste.

3 / 5

Actionability

Mostly executable, copy-paste-ready commands: 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.chargeblast.io/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --input \'{"key": "value"}\' --json', plus a concrete proxy flag table and a populated popular-actions table. Not a 5 because several examples rely on unresolved placeholders (CONNECTION_ID, QUERY, <id>) with no worked example showing how to obtain and substitute them.

4 / 5

Workflow Clarity

A real sequence exists (install → login → connection ensure → poll state → search actions → run → proxy fallback) with good state-machine handling ('READY', 'BUILDING', 'CLIENT_ACTION_REQUIRED', 'CONFIGURATION_ERROR'), but it breaks down at the seams: 'If the returned connection has state: "READY", skip to **Step 2**' points to a step that is never defined, and section '1b' has no matching '1a'. Additionally the skill covers consequential operations (unenroll-merchant, update-alert, upload-orders batch upload) with no validation/verification guidance, which caps this dimension at 3.

3 / 5

Progressive Disclosure

The skill is a single self-contained file (~155 lines) with no bundle files (no references/, scripts/, or assets/ directories exist), and the body makes no dangling file references. Sections are well-organized (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with the bulk-detail content (action catalog, proxy flags) appropriately in tables. Minor gaps — the overview/action-catalog split is slightly inconsistent — keep it below 5.

4 / 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 names the target app and includes an explicit 'Use when' trigger, but describes capabilities in purely generic terms. It reads like a template ('Manage data, records, and automate workflows') with no mention of the payment/dispute/merchant functionality the skill actually covers.

Suggestions

Replace the generic phrase 'Manage data, records, and automate workflows' with the skill's concrete operations, e.g. 'Manage merchants, orders, and dispute alerts; enroll/unenroll merchants in alert programs (Ethoca, CDRN, RDR); upload orders for chargeback matching'.

Add natural trigger synonyms users would say, such as 'chargebacks', 'disputes', 'alerts', or 'refund requests', so the description matches how users actually refer to Chargeblast workflows.

Tighten the trigger clause to cover the specific tasks, e.g. 'Use when the user wants to manage Chargeblast merchants, orders, or dispute/chargeback alerts'.

DimensionReasoningScore

Specificity

The domain is named ('Chargeblast integration') but the stated actions — 'Manage data, records, and automate workflows' — are minimal and generic, mirroring the anchor example 'Processes PDF files'. No concrete operations (merchants, alerts, disputes, orders) that the skill actually supports are mentioned.

2 / 5

Completeness

Both parts are present: a 'what' ('Chargeblast integration. Manage data, records, and automate workflows') and an explicit trigger clause ('Use when the user wants to interact with Chargeblast data'). Not a 5 because the 'what' is vague — it omits the actual capabilities (managing merchants, alerts, disputes) — and not a 3 because the 'when' is explicitly stated rather than implied.

4 / 5

Trigger Term Quality

The only natural keyword is the app name itself ('Chargeblast', 'Chargeblast data'), which users would say, but there are no synonyms, feature terms, or related phrases (payments, disputes, chargebacks, alerts). Matches 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The distinctive app name 'Chargeblast' appears in both the capability and trigger clauses, giving it a clear niche. Minor overlap risk remains because 'Manage data, records, and automate workflows' is generic enough to match other data-management or automation skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.