CtrlK
BlogDocsLog inGet started
Tessl Logo

chargeover

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

60

Quality

71%

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/chargeover/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 body is a well-structured, highly actionable guide with concrete CLI commands and a genuine polling/validation feedback loop for connection setup. Its main weaknesses are minor over-explanation in the intro and a large inline actions table that hints at progressive-disclosure opportunity.

DimensionReasoningScore

Conciseness

The body is mostly lean, leading with executable commands and only brief framing; the opening paragraph describing ChargeOver as a subscription billing platform is mild over-explanation that could be trimmed.

4 / 5

Actionability

Copy-paste-ready bash commands are provided throughout (install, login, connection ensure, action list/run, request) with JSON input examples and a populated actions table, fully covering common cases.

5 / 5

Workflow Clarity

The connection setup has a clear sequence with a polling feedback loop and state-based branching (READY / CLIENT_ACTION_REQUIRED / error), though the later search-then-run flow is less explicitly sequenced and the 'Step 2' reference is loosely labeled.

4 / 5

Progressive Disclosure

Content is well-organized under clear headers in a self-contained file with no nested references, though the popular-actions table is a sizable inline block that could arguably live in a reference file.

4 / 5

Total

17

/

20

Passed

Description

61%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 ChargeOver niche and includes an explicit 'Use when' trigger, but the capability actions are generic ('manage data, records') rather than concrete billing/subscription operations. It is distinctive but light on specific capability detail.

Suggestions

Replace generic actions with concrete ChargeOver operations, e.g. 'Manage customers, subscriptions, invoices, and payments in ChargeOver.'

Expand the trigger clause to mention recurring billing, invoicing, or subscription-lifecycle keywords users would naturally say.

Add a reference to the underlying entities (subscriptions, invoices, transactions) to sharpen what the skill does.

DimensionReasoningScore

Specificity

Names the ChargeOver domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete operations, matching the anchor for domain-named-but-generic actions.

2 / 5

Completeness

Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with ChargeOver data') are present, though the 'what' is generic and the 'when' could be more specific.

4 / 5

Trigger Term Quality

The primary natural trigger 'ChargeOver' is present alongside 'data' and 'records', but common variations or synonyms are missing, fitting the anchor for some relevant keywords with gaps.

3 / 5

Distinctiveness Conflict Risk

ChargeOver is a clearly niche platform with a distinct trigger term, giving it minimal overlap risk with other skills.

5 / 5

Total

14

/

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.