2checkout
2Checkout integration. Manage data, records, and automate workflows. Use when the user wants to interact with 2Checkout data.
44
46%
Does it follow best practices?
Impact
—
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 relies almost entirely on the '2Checkout' brand name for specificity and distinctiveness, while the actual capability description is generic boilerplate ('manage data, records, and automate workflows') that could apply to virtually any integration. It has the structural completeness of a 'what' and 'when' clause, but both are too vague to be truly useful for skill selection among many similar integration skills.
Suggestions
Replace generic 'manage data, records, and automate workflows' with specific 2Checkout actions like 'process payments, manage subscriptions, retrieve order details, handle refunds, generate invoices'.
Add natural trigger terms users would say, such as 'payments', 'subscriptions', 'invoices', 'orders', 'Avangate', '2CO', 'checkout integration'.
Make the 'Use when' clause more specific, e.g., 'Use when the user mentions 2Checkout, 2CO, or needs to manage online payments, subscriptions, or e-commerce transactions 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 specific, 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 skills. Without specific 2Checkout operations, it's only the brand name providing differentiation. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a generic Membrane CLI integration template with '2Checkout' substituted in. It lacks 2Checkout-specific actionable content — no concrete examples of managing products, orders, accounts, or subscriptions. The opening explanation of what 2Checkout is wastes tokens, and the 'Popular actions' section paradoxically contains no actual popular actions.
Suggestions
Remove the introductory paragraph explaining what 2Checkout is — Claude already knows this. Replace with 2Checkout-specific API patterns or gotchas.
Add concrete 2Checkout-specific examples: e.g., listing products, creating an order, managing a subscription, with actual action IDs and input/output schemas.
Factor out generic Membrane CLI instructions (install, auth, connection, proxy) into a shared reference file, keeping only 2Checkout-specific content in this SKILL.md.
Populate the 'Popular actions' section with actual 2Checkout actions (with example inputs/outputs) instead of just telling the user to discover them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what 2Checkout is ('Think of it as an alternative to Stripe or PayPal') — Claude already knows this. The overview section lists four bullet points (Product, Account, Order, Insight) with no actionable content. There's significant boilerplate about Membrane CLI that is generic across all Membrane integrations and not specific to 2Checkout. | 1 / 3 |
Actionability | The skill provides concrete CLI commands for authentication, connection setup, action discovery, and proxy requests, which are copy-paste ready. However, there are no 2Checkout-specific examples (e.g., creating an order, listing products, managing subscriptions) — the 'Popular actions' section just tells you to discover them yourself, making the guidance incomplete for the stated purpose. | 2 / 3 |
Workflow Clarity | The connection setup workflow is reasonably well-sequenced with state handling (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) and polling instructions. However, there are no validation checkpoints for the actual 2Checkout operations (e.g., verifying an order was created correctly), and the overall workflow from connection to performing actual 2Checkout tasks lacks a clear end-to-end sequence. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but it's a monolithic file with no references to supporting files. The Membrane CLI generic instructions (authentication, connection setup, proxy requests) could be factored out into a shared reference, keeping only 2Checkout-specific guidance in this skill. No bundle files are provided to support progressive disclosure. | 2 / 3 |
Total | 7 / 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
f484c82
- 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.