adyen
Adyen integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adyen data.
61
52%
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/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.
The description relies heavily on the 'Adyen' brand name for identification but fails to describe what specific Adyen capabilities are supported. The actions listed ('manage data, records, and automate workflows') are boilerplate phrases that could apply to virtually any integration. It needs concrete Adyen-specific actions and richer trigger terms related to payment processing.
Suggestions
Replace vague actions with specific Adyen operations, e.g., 'Process payments, manage refunds, configure webhooks, retrieve transaction details, and handle payouts through Adyen.'
Add natural trigger terms users would say, such as 'payments', 'transactions', 'refunds', 'checkout', 'payment gateway', 'Adyen API'.
Expand the 'Use when' clause with specific scenarios, e.g., 'Use when the user mentions Adyen, payment processing, transaction management, refunds, or needs to integrate with Adyen's payment platform.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. It doesn't mention specific Adyen operations like processing payments, managing refunds, creating payouts, or configuring webhooks. | 1 / 3 |
Completeness | It has a 'Use when' clause ('Use when the user wants to interact with Adyen data'), satisfying the 'when' requirement, but the 'what' is extremely vague ('manage data, records, and automate workflows' could apply to almost any integration). The 'when' clause itself is also very generic. | 2 / 3 |
Trigger Term Quality | It includes 'Adyen' as a key trigger term and 'data' which is generic. However, it misses natural terms users would say like 'payments', 'transactions', 'refunds', 'payouts', 'checkout', or 'payment processing'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Adyen' as a proper noun provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with any data management or integration skill. Without payment-specific terminology, it could conflict with 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.
The skill provides solid, actionable CLI commands for integrating with Adyen via Membrane, making it practically useful. However, it wastes tokens on explaining what Adyen is and includes a shallow entity overview that adds no actionable value. Workflow clarity would benefit from explicit error handling guidance and validation steps beyond the action creation polling.
Suggestions
Remove the opening paragraph explaining what Adyen is — Claude already knows this — and remove or enrich the entity bullet list with actionable links or details.
Add explicit error handling/validation steps for key operations like `membrane connect` failures and `membrane action run` error responses.
Consider linking the entity overview items (Payment, Refund, etc.) to example action queries or common workflows to make them actionable rather than decorative.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Adyen is (global payment platform, etc.) is unnecessary context Claude already knows. The overview bullet list of entities adds little value without actionable detail. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Each command includes concrete flags and placeholders. | 3 / 3 |
Workflow Clarity | The multi-step workflows (install → authenticate → connect → discover → create/run) are present and sequenced, but there are no explicit validation checkpoints or error recovery loops beyond the action creation polling. For example, there's no guidance on what to do if `membrane connect` fails or if action run returns an error. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but it's somewhat monolithic — all content is inline in a single file with no references to separate detailed docs (beyond the generic Adyen docs link). The overview bullet list hints at structure but doesn't link to anything actionable. | 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 | |
- Repository
- membranedev/application-skills
- Commit
56d7336
- 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.