adyen
Adyen integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adyen data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill adyen61
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
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description identifies the integration target (Adyen) but fails to specify what concrete actions the skill enables. The vague 'manage data, records, and automate workflows' language could apply to almost any integration skill. Without specific payment-related capabilities and trigger terms, Claude would struggle to select this skill appropriately.
Suggestions
Replace vague language with specific Adyen capabilities like 'Process payments, manage refunds, retrieve transaction history, configure webhooks'
Add payment-related trigger terms users would naturally say: 'payments', 'transactions', 'refunds', 'checkout', 'payment processing'
Expand the 'Use when...' clause to include specific scenarios: 'Use when the user mentions Adyen, payment processing, transaction lookups, or refund management'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what specific Adyen operations are supported (e.g., process payments, manage subscriptions, handle refunds). | 1 / 3 |
Completeness | Has a 'Use when...' clause which addresses the 'when' question, but the 'what' is extremely vague. The trigger guidance 'interact with Adyen data' is too generic to be useful for skill selection. | 2 / 3 |
Trigger Term Quality | Includes 'Adyen' as a key trigger term and 'Adyen data', but misses natural payment-related keywords users might say like 'payments', 'transactions', 'refunds', 'checkout', or 'payment gateway'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Adyen' provides some distinctiveness as a specific platform name, but 'Manage data, records, and automate workflows' is generic enough to overlap with many other integration skills. | 2 / 3 |
Total | 7 / 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 Adyen integration via Membrane, with good coverage of connection setup, action discovery, and proxy requests. However, it wastes tokens explaining what Adyen is, includes an unhelpful entity list without context, and lacks validation steps for confirming successful operations.
Suggestions
Remove the opening paragraph explaining what Adyen is - Claude already knows this
Either remove the 'Adyen Overview' entity list or add actionable context explaining when/how to use each entity type
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID') and after action runs
Add error handling guidance for common failures like authentication errors or invalid action IDs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Adyen is wastes tokens on information Claude already knows. The CLI setup and connection instructions are reasonably efficient, but the overview section listing entities without context adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including JSON parameter passing, proxy requests with flag documentation, and step-by-step connection setup. Commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are listed but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the entity overview (Payment, Checkout Configuration, etc.) is unexplained and unhelpful. No references to external files for advanced topics or detailed API documentation. | 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.