2checkout
2Checkout integration. Manage data, records, and automate workflows. Use when the user wants to interact with 2Checkout data.
73
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/2checkout/SKILL.mdQuality
Discovery
57%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 identifies the platform (2Checkout) and includes an explicit 'Use when' clause, but the capabilities listed are extremely generic and could apply to virtually any integration skill. It lacks specific actions like managing subscriptions, processing payments, or handling refunds that would help Claude understand when to select this skill over others.
Suggestions
Replace generic phrases like 'manage data, records, and automate workflows' with specific 2Checkout actions such as 'process payments, manage subscriptions, retrieve order details, handle refunds'.
Add natural trigger terms users might say, such as 'payment processing', 'subscriptions', 'invoices', 'Avangate', '2CO', or 'online payments'.
Make the 'Use when' clause more specific, e.g., 'Use when the user mentions 2Checkout, 2CO, or needs to manage online payment processing, subscriptions, or order data through 2Checkout's platform'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to 2Checkout. It doesn't mention specific operations like processing payments, managing subscriptions, handling invoices, or retrieving order details. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with 2Checkout data), with an explicit 'Use when' clause. However, both parts are quite generic. | 3 / 3 |
Trigger Term Quality | It includes '2Checkout' as a key trigger term, which is relevant, but misses natural variations users might say such as 'payment processing', 'subscriptions', 'invoices', 'orders', 'Avangate', or '2CO'. | 2 / 3 |
Distinctiveness Conflict Risk | The '2Checkout' mention provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many other integration or data management skills. Only the platform name differentiates it. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a solid, actionable workflow for integrating with 2Checkout via the Membrane CLI, with clear state-handling logic and concrete commands. Its main weaknesses are unnecessary introductory content explaining what 2Checkout is, a vacuous overview section, and some redundancy. Trimming the fluff and removing the empty 'Popular actions' section would improve token efficiency.
Suggestions
Remove the opening paragraph explaining what 2Checkout is — Claude already knows this, and it wastes tokens.
Remove or flesh out the '2Checkout Overview' section (Product/Account/Order/Insight) — as-is, it provides zero actionable information.
Remove or repurpose the 'Popular actions' heading, which just repeats the discovery command already shown above.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what 2Checkout is (a payment platform, alternative to Stripe/PayPal) — Claude already knows this. The '2Checkout Overview' section listing Product/Account/Order/Insight with no detail adds no value. However, the CLI workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection management, action discovery, action creation, and execution. Input parameters and flags are clearly specified with examples. | 3 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced: install CLI → authenticate → ensure connection → wait/poll for readiness → search actions → create if needed → run. State handling (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) is explicitly documented with clear next steps for each state, forming effective feedback loops. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat long and monolithic for a single file. The '2Checkout Overview' section with just four bullet points adds nothing, and the 'Popular actions' section is essentially empty — just repeating a discovery command. No references to external files for advanced topics. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
88db8c5
- 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.