ClawHub

Lap Adyen Payment Api

v1.0.0

Adyen Payment API skill. Use when working with Adyen Payment for adjustAuthorisation, authorise, authorise3d. Covers 13 endpoints.

⭐ 0· 41·0 current·0 all-time
by@mickmicksh
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
CryptoCan make purchasesRequires OAuth token
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description describe Adyen payment endpoints and the SKILL.md documents those endpoints. The single required env var ADYEN_PAYMENT_API_KEY is appropriate for an API wrapper that calls Adyen.
ℹ
Instruction Scope
Runtime instructions are limited to calling Adyen endpoints and referencing a generated spec file (references/api-spec.lap). They do not ask the agent to read unrelated files or credentials. Minor inconsistency: Auth section lists both "ApiKey X-API-Key" and "Bearer", while Setup instructs to "Set Authorization header with your Bearer token" even though the declared env var is ADYEN_PAYMENT_API_KEY (suggests X-API-Key). This is a documentation mismatch to verify before use.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is written to disk or downloaded by the skill itself.
✓
Credentials
Only one environment variable (ADYEN_PAYMENT_API_KEY) is requested, which is proportional to the stated purpose. No unrelated secrets or system config paths are requested.
✓
Persistence & Privilege
always:false and no install behavior. The skill can be invoked autonomously (platform default) but does not request elevated or persistent system privileges.
Assessment
This skill appears coherent for calling Adyen test endpoints and only needs your Adyen API key. Before installing: 1) Verify whether your integration expects an X-API-Key header (API key) or a Bearer token — the SKILL.md mixes the two; supply the appropriate credential and avoid giving production keys until validated. 2) Confirm where references/api-spec.lap is sourced from (the skill references it but does not include it). 3) Use a test/restricted API key initially and ensure the key has minimal permissions (and rotate it if you later remove the skill). 4) Note the base URL points to Adyen's pal-test endpoint; if you switch to production, double-check the endpoints and auth method.

Like a lobster shell, security has layers — review code before you run it.

latestvk978tbezrewt023etn2v5v5py984a21e

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

EnvADYEN_PAYMENT_API_KEY

Comments