Acf
v1.0.2ACF integration. Manage data, records, and automate workflows. Use when the user wants to interact with ACF data.
⭐ 0· 117·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
medium confidencePurpose & Capability
The skill's name/description (ACF integration) align with the instructions, which use Membrane to interact with ACF. However, the registry metadata declares no required binaries while the SKILL.md explicitly instructs installing the @membranehq/cli (via npm) and running membrane commands — a small inconsistency to be aware of.
Instruction Scope
Instructions are focused on using Membrane CLI to discover connectors/actions, run actions, and proxy API requests to ACF. They do not instruct reading arbitrary local files or requesting unrelated credentials. They do rely on browser-based authentication or headless token completion, which is expected for this workflow.
Install Mechanism
Install steps instruct using npm (npm install -g @membranehq/cli or npx). npm is a public package registry (moderate risk compared to OS package managers). No downloads from unusual URLs or archives are suggested. Confirm you trust the @membranehq/cli package on npm before installing globally.
Credentials
The skill does not request environment variables or local credentials; it relies on Membrane's managed connections and browser-based auth. This is proportionate for an integration that needs authenticated access to ACF.
Persistence & Privilege
The skill does not request always:true, does not declare config paths, and is instruction-only. The only persistent change the SKILL.md suggests is installing a global CLI (user choice). Autonomous invocation is allowed by default but is not combined with other concerning privileges here.
Assessment
This skill appears to be what it says: an ACF integration that uses the Membrane CLI. Before installing, (1) ensure you are comfortable installing a global npm package (Node/npm required); (2) verify the @membranehq/cli package on npm and the Membrane service (https://getmembrane.com) are legitimate and acceptable to your organization; (3) be aware authentication occurs through Membrane (browser flow or headless completion) — the CLI and service will be able to proxy requests to your ACF endpoints, so only grant access if you trust Membrane to handle those credentials; and (4) note the registry metadata omitted the CLI requirement — ask the publisher to include required binaries (npm/node) in metadata if you need stricter inventory control.Like a lobster shell, security has layers — review code before you run it.
latestvk9777cv3d5x0xcdffqef6grbp98437z1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.