2checkout
2Checkout integration. Manage data, records, and automate workflows. Use when the user wants to interact with 2Checkout data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 2checkout72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 includes a 'Use when' clause and identifies the integration target (2Checkout), but suffers from overly generic capability descriptions that don't reflect what 2Checkout actually does (payment processing, subscriptions, order management). The trigger terms are minimal, relying solely on the brand name without including related payment/commerce terminology users might naturally use.
Suggestions
Replace generic actions with 2Checkout-specific capabilities like 'process payments, manage subscriptions, handle refunds, retrieve order history, generate invoices'
Add natural trigger terms users would say: 'payments', 'subscriptions', 'checkout', 'billing', 'orders', 'refunds'
Expand the 'Use when' clause to include specific scenarios: 'Use when the user mentions 2Checkout, payment processing, subscription management, or needs to handle online transactions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (2Checkout) and mentions general actions ('Manage data, records, and automate workflows'), but these actions are generic and not specific to what 2Checkout actually does (e.g., payment processing, subscriptions, invoices). | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with 2Checkout data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes '2Checkout' as a trigger term which users would say, but misses common variations and related terms like 'payments', 'subscriptions', 'checkout', 'billing', or 'Verifone' (2Checkout's parent company). | 2 / 3 |
Distinctiveness Conflict Risk | The '2Checkout' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many other integration skills. Could conflict with other payment or e-commerce integrations. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for 2Checkout integration via Membrane, with good coverage of common operations. However, it wastes tokens explaining what 2Checkout is, lacks validation/error handling in workflows, and the Overview section is underdeveloped. The structure is adequate but could benefit from clearer decision points and external references for advanced use cases.
Suggestions
Remove or drastically shorten the opening paragraph explaining what 2Checkout is - Claude already knows this
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Expand the Overview section with actual links or brief descriptions, or remove it entirely if it adds no value
Add error handling guidance: what to do if connection fails, if action returns an error, or if credentials expire
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what 2Checkout is wastes tokens on information Claude already knows. The rest is reasonably efficient but could be tightened (e.g., the 'Overview' section with just four bullet points adds little value). | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax, flags documented in a table, and copy-paste ready examples for all major operations including connection setup, action discovery, and proxy requests. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No error handling or feedback loops for failed connections or actions. The workflow for checking existing connections vs creating new ones could be clearer as a decision tree. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The 'Overview' section lists four items without explanation or links. No references to external documentation for advanced topics like subscription management or webhook handling. | 2 / 3 |
Total | 9 / 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 | |
- 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.