ClawHub

Adbutler

v1.0.0

AdButler integration. Manage data, records, and automate workflows. Use when the user wants to interact with AdButler data.

⭐ 0· 34·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (AdButler integration) matches the instructions: everything is about using the Membrane CLI to connect to AdButler, discover actions, run them, or proxy raw AdButler API calls. Nothing requested in the SKILL.md appears unrelated to AdButler integration.
✓
Instruction Scope
Runtime instructions are limited to: install/run the Membrane CLI, perform membrane login (browser-based), list/connect to connectors, run actions, and proxy requests. The instructions do not ask the agent to read local secrets, arbitrary files, or other system configuration. They do allow raw proxied HTTP requests via Membrane (expected for a proxy feature).
ℹ
Install Mechanism
There is no registry install spec, but SKILL.md tells users to install @membranehq/cli globally via npm. Installing a global npm package is common for CLIs but carries the usual supply-chain risk of npm packages (verify publisher, package name, and versions). The skill itself does not perform any install in the registry metadata.
✓
Credentials
The skill declares no required env vars or credentials and explicitly instructs not to ask users for API keys, instead using Membrane connections. No unrelated credentials or config paths are requested.
✓
Persistence & Privilege
The skill is not marked always:true and has no install-time modifications or system-wide configuration changes. It relies on the Membrane CLI and the user's Membrane account for authentication and proxying.
Assessment
This skill is coherent: it expects you to use the Membrane CLI to connect to AdButler and does not request unrelated secrets. Before installing/running anything: (1) verify you trust Membrane (getmembrane.com) and the npm package @membranehq/cli (check the npm page and the GitHub repo for the project), (2) be aware that using the Membrane proxy means requests and AdButler credentials are handled by Membrane servers (review their privacy/security documentation), and (3) be cautious when installing global npm packages—confirm the package name/version to avoid typosquatting. If you want stronger assurance, inspect the @membranehq/cli source on GitHub and the Membrane privacy/security docs before using this skill.

Like a lobster shell, security has layers — review code before you run it.

latestvk9799m1w25db7n3wh5gs1veats847451

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments