Name: checkoutcom
Rating: 56.8 (1 reviews)
Author: membranedev

checkoutcom

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/checkoutcom/SKILL.md

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 content is a well-structured, actionable guide with concrete CLI commands and a genuine connection-readiness feedback loop. Its weak points are some redundant or padded sections and a dangling "Step 2" cross-reference that slightly disrupts the workflow sequence.

Suggestions

Remove the redundant "Popular actions" section that repeats the action-list command already given under "Searching for actions", or fold it into a single discovery section.

Fix the dangling "skip to Step 2" reference by adding a numbered "Step 2" heading (or rewording the forward references) so the workflow sequence is unambiguous.

Trim the introductory paragraph describing what Checkout.com is, since it explains product context Claude can infer, keeping only the integration-relevant detail.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes some padding: the introductory paragraph explaining what Checkout.com is and a redundant "Popular actions" section that repeats the action-list command already shown, fitting the anchor for mostly-efficient content with some unnecessary explanation that could be tightened.	3 / 5
Actionability	It provides copy-paste-ready commands for the common cases (install, login, connection ensure, wait-poll, action list/run, proxy with a flags table), with minor gaps such as the CONNECTION_ID placeholder requiring prior steps and no concrete example with a real actionId, matching the mostly-executable anchor.	4 / 5
Workflow Clarity	The install-to-login-to-connect-to-search-to-run sequence is clear and includes an explicit feedback loop around connection state (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but the dangling "skip to Step 2" reference (no actual Step 2 heading) leaves a minor sequencing gap, fitting the clear-sequence anchor with most checkpoints present.	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives in one well-sectioned SKILL.md with clear headers, but some inline detail such as the proxy flags table and action schema descriptions could be split into reference files, fitting the good-structure anchor with minor organization gaps.	4 / 5
	Total	15 / 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 is clear and third-person with an explicit "Use when" trigger, naming a distinct product niche. Its main weakness is generic action verbs and a broad trigger clause rather than concrete, varied trigger phrases.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Checkout.com capabilities such as "authorize and capture payments, process refunds, and handle disputes and webhooks".

Expand the trigger clause with concrete phrases users would say, e.g. "Use when the user wants to process payments, issue refunds, or handle Checkout.com disputes and webhooks".

Add natural keyword variations (e.g. "payments", "refunds", "Checkout.com API") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Checkout.com integration") and lists several actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete API-level capabilities, fitting the anchor that names a domain with 1-2 actions but is not comprehensive.	3 / 5
Completeness	It states both what the skill does ("Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with Checkout.com data"), but the "when" clause is generic rather than listing concrete triggers, matching the anchor for both present with the "when" only partially specific.	4 / 5
Trigger Term Quality	It includes the domain keyword "Checkout.com" and a "Use when the user wants to interact with Checkout.com data" trigger, but offers few natural synonyms or variations a user would say, matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ("Checkout.com integration") gives it a clear niche with minimal conflict risk, though the broad "interact with Checkout.com data" trigger leaves minor overlap risk with closely related payment skills, fitting the mostly-distinct anchor.	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/checkoutcom/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.