Airbyte
v1.0.2Airbyte integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airbyte data.
⭐ 0· 80·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 skill's name/description (Airbyte integration) matches the SKILL.md: it directs the agent to use the Membrane CLI to manage Airbyte connectors, connections, and proxy API requests. The actions and examples correspond to interacting with Airbyte through Membrane and are proportionate to the stated purpose.
Instruction Scope
All runtime instructions are limited to installing/using the Membrane CLI, logging in, listing/creating/updating connections, running Membrane actions, or proxying requests to the Airbyte API. The SKILL.md does not ask the agent to read arbitrary host files or unrelated environment variables. It does assume interactive authentication (browser-based login) and provides a headless fallback flow.
Install Mechanism
There is no formal install spec in the registry metadata, but the SKILL.md instructs users to run `npm install -g @membranehq/cli`. This is a standard npm install (traceable to the npm registry) but it requires Node/npm and will install a third‑party CLI globally — a system change the registry metadata doesn't declare. This is expected for an instruction-only skill but worth noting: global npm installs execute package install scripts and should be done only from trusted packages/sources.
Credentials
The skill declares no required env vars or credentials and instead relies on Membrane account authentication via the CLI. That is proportional: Membrane handles the service credentials and the SKILL.md explicitly instructs not to ask users for API keys. Be aware that the CLI will persist auth state locally (so the agent/host account that runs the CLI will have access to those tokens).
Persistence & Privilege
The skill is not always-enabled and uses the default autonomous-invocation setting. The SKILL.md expects an authenticated Membrane CLI; the CLI stores credentials locally, which means any agent process that can run the CLI may use those credentials. This is normal for CLI-based integrations but worth considering if you share the host or agent environment.
Assessment
This skill is coherent with its Airbyte purpose and uses the Membrane CLI to proxy requests and manage connectors. Before installing/using it: (1) confirm you trust the @membranehq/cli npm package (review its npm page and repository), (2) be aware that `npm install -g` will modify the host environment and runs package install scripts, and (3) understand that the Membrane CLI stores authentication tokens locally — any agent or user account that can run the CLI can act with those credentials. If you do not want to install a third‑party CLI or share local auth state, do not enable this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk97a4f96bvt0bak0jmfekw377h8423gb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.