Acquia
v1.0.2Acquia integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acquia data.
⭐ 0· 101·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 declares an Acquia integration and all runtime instructions show use of the Membrane CLI to connect to and proxy requests to Acquia; there are no unrelated credential or binary requirements.
Instruction Scope
SKILL.md only instructs installing the Membrane CLI, logging in, creating/using a Membrane connection, listing/ running actions, and optionally proxying API requests through Membrane. It does not ask the agent to read unrelated files, environment variables, or system secrets.
Install Mechanism
There is no formal install spec; the doc tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a standard but moderately privileged action (writes to system PATH). This is not unusual for a CLI-based integration, but users should verify the npm package's trustworthiness before installing globally.
Credentials
No environment variables or credentials are requested by the skill. SKILL.md explicitly recommends using Membrane to handle authentication server-side, which matches the declared zero-env design.
Persistence & Privilege
The skill is not force-included (always:false) and does not request persistent system-wide changes or access to other skills' configs. Autonomous invocation is allowed (default) but is not combined with other red flags here.
Assessment
This skill is internally coherent: it expects you to install and use the Membrane CLI to talk to Acquia and relies on Membrane to hold credentials. Before installing or using it, verify that you trust @membranehq/cli (check the npm package, GitHub repo, and privacy/security docs) because API requests and credentials will be proxied through Membrane's service. Prefer installing CLIs without using root/global if possible (use a node version manager or container) and be aware that 'membrane login' opens a browser flow and that proxying requests means Membrane will see request/response data to/from Acquia. If you need a higher assurance level, review Membrane's security, data retention, and access controls before granting it access to your Acquia environment.Like a lobster shell, security has layers — review code before you run it.
latestvk972jk9y9037vm54b7rfz2q8k9843g7z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.