Amadeus
v1.0.0Amadeus integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amadeus data.
⭐ 0· 64·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description state 'Amadeus integration' and the SKILL.md consistently instructs using Membrane to connect to Amadeus and run actions or proxy requests. No unrelated environment variables, binaries, or config paths are requested.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, logging in (browser-based), creating a connector/connection, listing actions, running actions, or proxying requests to Amadeus. The document does not instruct the agent to read unrelated files, access other credentials, or transmit data to unexpected endpoints.
Install Mechanism
There is no embedded install spec; the README suggests installing the official @membranehq/cli via npm (global install). This is proportionate for a CLI-driven workflow. Note: a global npm install needs appropriate system privileges and trusts the npm package.
Credentials
The skill declares no required env vars or primary credential and explicitly instructs not to request API keys from users, relying on Membrane for auth. Requested access is minimal and aligned with the stated purpose.
Persistence & Privilege
The skill is not always-enabled and uses default autonomous invocation settings. It does not request persistent system configuration or modify other skills. No elevated privileges are requested.
Assessment
This skill is coherent: it simply instructs the agent to use the Membrane CLI to talk to Amadeus. Before installing or running it, consider that Membrane (a third-party service) will proxy requests and manage Amadeus credentials — verify you trust https://getmembrane.com and the @membranehq/cli npm package and review their privacy/security documentation. Installing the CLI with npm -g requires appropriate system permissions, so run in a controlled environment or use a non-global install if preferred. If you need to limit exposure, create a dedicated Membrane account/connection with least privilege for the tasks you intend to perform.Like a lobster shell, security has layers — review code before you run it.
latestvk97bzxts2pnyjbxm829kess27s84bt84
License
MIT-0
Free to use, modify, and redistribute. No attribution required.