CtrlK
BlogDocsLog inGet started
Tessl Logo

chargent

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

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

82%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 well-structured connection workflow including validation checkpoints. Its only notable gaps are an unresolved 'Step 2' cross-reference and minor verbosity in the opening overview.

Suggestions

Label or define the 'Step 2' referenced in the Connecting section so the cross-reference resolves to an actual section header.

Tighten the opening overview paragraph to drop product-marketing framing ('helps businesses manage recurring billing...') in favor of task-relevant context.

DimensionReasoningScore

Conciseness

The body is largely lean, command-driven, and assumes Claude's competence; only the opening marketing-style paragraph and a few explanatory asides could be trimmed, fitting the efficient-with-minor-over-explanation anchor.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands throughout (membrane login, connection ensure, action list/run, request) plus a complete flag table, covering the common cases concretely.

5 / 5

Workflow Clarity

The connection setup is clearly sequenced with explicit polling/state feedback loops (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but the referenced 'Step 2' is never labeled as a section, leaving a minor navigation gap.

4 / 5

Progressive Disclosure

Well-organized into clear sections with no nested or buried references and no bundle files, but all ~145 lines live inline in SKILL.md with some content (proxy flag table, best practices) that could arguably be split out.

4 / 5

Total

17

/

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 is third-person, includes an explicit 'Use when' trigger, and is highly distinct thanks to the named product. Its main weakness is generic action language that under-specifies what the skill concretely does.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with Chargent-specific actions such as 'process payments, manage recurring billing, and query Payment Request records'.

Add a couple of natural trigger variations beyond 'Chargent data', e.g. 'when the user mentions Chargent, recurring billing, or payment transactions in Salesforce'.

DimensionReasoningScore

Specificity

Names the domain (Chargent) and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete Chargent-specific operations, matching the anchor for 1-2 actions that are not comprehensive.

3 / 5

Completeness

Explicitly answers both what ("Chargent integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with Chargent data."); the when clause is present and clear but the what could be more specific, so it sits just below the top anchor.

4 / 5

Trigger Term Quality

Includes the relevant product keyword ("Chargent", "Chargent data") but offers limited variation or synonyms, fitting the anchor of some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

Chargent is a named, specific Salesforce payment product, giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

15

/

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.

Validation15 / 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
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.