CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

checkoutcom

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

Quality

64%

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/checkoutcom/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 solid, command-driven integration guide with executable examples, good state-handling feedback loops, and clear structure. Its main weaknesses are the padded introductory/overview sections that add nothing Claude doesn't know and a broken step-numbering reference ('Step 2' / '1b' without matching headings).

Suggestions

Delete or compress the opening 'Checkout.com is a payment processing platform...' paragraph and the 'Checkout.com Overview' bullet tree — Claude already knows what a payment processor is, and no command references them.

Fix the step numbering: either label 'Connecting to Checkout.com' as Step 1 and 'Searching for actions' as Step 2, or drop the 'skip to Step 2' and '1b' references in favor of section names.

DimensionReasoningScore

Conciseness

The body opens with a padded encyclopedic paragraph ('Checkout.com is a payment processing platform that helps online businesses accept and manage payments globally...') and a low-value bullet overview of concepts Claude already knows, though the command-focused sections are efficient.

3 / 5

Actionability

Concrete copy-paste commands throughout — install, login (including headless completion), 'connection ensure', 'action list/run' with JSON input, and a proxy flag table — with only minor gaps such as unfilled placeholders (CONNECTION_ID) and an unvalued '--tenant' flag.

4 / 5

Workflow Clarity

The sequence (install → login → connect → poll state → discover actions → run/proxy) is clear with genuine feedback loops (polling BUILDING, handling CLIENT_ACTION_REQUIRED and CONFIGURATION_ERROR), but the body references 'Step 2' and a '1b' step while no Step 1a/2 headings exist, which is a minor sequencing gap.

4 / 5

Progressive Disclosure

No bundle files exist and the ~140-line single-file body is well organized with clear section headers and a useful table; however, detail like the clientAction schema enumeration and the proxy flag reference could be split out, keeping it below the clear-split 5 anchor.

4 / 5

Total

15

/

20

Passed

Description

46%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 has a proper explicit 'Use when' clause but its capability statement is boilerplate-generic, naming no domain-specific actions or trigger keywords beyond the brand itself. A user asking about payments, refunds, disputes, or webhooks would not naturally match this description.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Checkout.com capabilities, e.g. 'Process payments, capture or void authorizations, issue refunds, manage disputes, and handle webhooks'.

Add natural trigger keywords to the 'Use when' clause: 'Use when the user mentions Checkout.com, payments, transactions, refunds, disputes, or payment webhooks'.

State the operational what more concretely (running pre-built API actions or proxying raw API requests via the Membrane CLI) so the description distinguishes itself from generic CRM/database integration skills.

DimensionReasoningScore

Specificity

The description names the domain ('Checkout.com integration') but the stated actions are purely generic — 'Manage data, records, and automate workflows' — with no concrete capabilities like payments, refunds, disputes, or webhooks, matching the anchor for minimal/generic actions.

2 / 5

Completeness

Both parts are explicitly present: what ('Checkout.com integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Checkout.com data'), but the 'when' clause is generic and could be more specific, so it cannot reach the 5 anchor.

4 / 5

Trigger Term Quality

Apart from the brand name 'Checkout.com', the only keywords are generic ('data', 'records', 'workflows'); natural user phrases such as 'payments', 'transactions', 'refunds', 'disputes', or 'webhooks' are entirely missing.

2 / 5

Distinctiveness Conflict Risk

'Checkout.com' is a distinct proper-noun trigger, but the templated generic body ('Manage data, records, and automate workflows') would overlap with any similarly structured integration skill, leaving it somewhat specific with residual overlap risk.

3 / 5

Total

11

/

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

Revision

f484c82

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill