Vies Api
v1.0.0VIES API integration. Manage data, records, and automate workflows. Use when the user wants to interact with VIES API data.
⭐ 0· 52·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill describes a VIES (VAT validation) integration and exclusively instructs use of the Membrane CLI and a Membrane account to connect and proxy requests to the VIES API. Required capabilities (network + Membrane account + Membrane CLI) match the described purpose.
Instruction Scope
SKILL.md stays on-topic: it instructs installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests. It does not instruct reading unrelated system files, exporting unrelated credentials, or contacting unexpected external endpoints beyond Membrane and the VIES API.
Install Mechanism
This is an instruction-only skill with no install spec, but it tells users to globally install @membranehq/cli via npm and to use npx for commands. Installing global npm packages is a common and reasonable requirement here, but global npm installs run package install scripts and should be treated like any third-party tool install (verify package provenance, consider using a container or non-root environment).
Credentials
The skill declares no required env vars or credentials and relies on Membrane-managed connections. This is proportionate: the integration uses Membrane to handle auth and therefore does not ask for unrelated secrets.
Persistence & Privilege
The skill is not always-enabled and does not request persistent privileges or modify other skills/configurations. It is user-invocable and allows normal autonomous invocation (default), which is expected for skills of this type.
Assessment
Before installing/using: (1) Understand that the skill expects you to install and run the Membrane CLI (npm install -g @membranehq/cli or use npx). Global npm installs execute package scripts—verify the package on npm/GitHub and consider installing in a container or non-root environment. (2) You will need a Membrane account and to authenticate via browser; Membrane will proxy requests and manage credentials server-side—so VAT numbers and request payloads are routed through Membrane’s infrastructure. If that matters for privacy or compliance, review Membrane’s privacy/security docs and the connector’s permissions. (3) The skill itself is instruction-only (no code bundled), so risks come from the tools you choose to install and from sending data through Membrane rather than from hidden code in the skill.Like a lobster shell, security has layers — review code before you run it.
latestvk9711sdkyddpegfad4ev8wn74n84czks
License
MIT-0
Free to use, modify, and redistribute. No attribution required.