adyen
Adyen integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adyen data.
44
45%
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/adyen/SKILL.mdQuality
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 is too vague and generic to effectively guide skill selection. While it correctly identifies Adyen as the domain and includes a 'Use when' clause, the actual capabilities described ('manage data, records, and automate workflows') are boilerplate language that could apply to any integration. It fails to communicate what specific Adyen operations this skill supports.
Suggestions
Replace generic phrases like 'manage data, records, and automate workflows' with specific Adyen capabilities such as 'process payments, manage refunds, configure webhooks, retrieve transaction details, and handle payouts'.
Expand trigger terms in the 'Use when' clause to include natural user language like 'payments', 'transactions', 'refunds', 'checkout', 'merchant account', or 'payment gateway'.
Add specificity about which Adyen APIs or features are supported to distinguish this from other payment or integration skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to Adyen. There are no specific capabilities mentioned such as processing payments, managing refunds, creating payouts, or configuring webhooks. | 1 / 3 |
Completeness | It has a weak 'what' (manage data, records, automate workflows) and a 'when' clause ('Use when the user wants to interact with Adyen data'), but the 'what' is too generic to be meaningful and the 'when' merely restates the vague description rather than providing explicit triggers. | 2 / 3 |
Trigger Term Quality | It includes 'Adyen' as a key trigger term and 'data' and 'workflows', but misses natural user terms like 'payments', 'transactions', 'refunds', 'payouts', 'merchant account', or 'checkout' that users would commonly say when needing Adyen integration help. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with many other integration skills. The mention of 'Adyen' provides some distinctiveness, but the rest of the description could apply to virtually any data management or integration skill. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides strong actionable CLI commands for Adyen integration via Membrane, but is undermined by verbosity — particularly the introductory explanation of Adyen and redundant descriptions of concepts Claude already knows. The workflow for connection setup is reasonably clear but lacks explicit validation steps, and the content would benefit from being split across files for better progressive disclosure.
Suggestions
Remove the introductory paragraph explaining what Adyen is and the 'Adyen Overview' bullet list — Claude already knows this and it wastes tokens.
Trim explanatory prose around Membrane concepts (auth lifecycle, credential refresh, OAuth) to just the essential commands and flags.
Add explicit validation/verification steps after running actions (e.g., 'Verify the output field contains expected data before proceeding').
Extract the proxy request options table and connection state machine details into separate reference files, keeping SKILL.md as a concise overview with links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Adyen is and what payment platforms do — information Claude already knows. The Membrane CLI setup, authentication flow, and connection state machine are verbose with extensive explanations of concepts like OAuth and credential refresh that Claude understands. The 'Adyen Overview' bullet list adds no actionable value. | 1 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection creation, action discovery, action execution, and proxy requests. Commands include concrete flags, JSON output options, and parameter passing examples that are copy-paste ready. | 3 / 3 |
Workflow Clarity | The connection setup workflow has a clear sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but there are no explicit validation checkpoints or error recovery feedback loops for the overall integration workflow. The steps for discovering and running actions are listed but lack a cohesive end-to-end workflow with verification. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but it's a monolithic document with no references to supporting files. The proxy request options table, connection state machine details, and best practices could be split into separate reference files. The 'Adyen Overview' section lists entities but provides no navigation or links to detailed documentation. | 2 / 3 |
Total | 8 / 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.