Adshares
v1.0.0AdShares integration. Manage data, records, and automate workflows. Use when the user wants to interact with AdShares data.
⭐ 0· 90·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
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The skill says it integrates AdShares and all runtime instructions center on the Membrane CLI and Membrane-managed connections to AdShares. Requiring the Membrane CLI and a Membrane account is proportionate to the stated purpose.
Instruction Scope
SKILL.md only instructs the agent/operator to install and use @membranehq/cli, run Membrane commands (login, connect, action list/run, request proxy). It does not instruct reading unrelated files/paths or exfiltrating local environment data. It explicitly recommends letting Membrane manage credentials rather than collecting API keys locally.
Install Mechanism
There is no formal install spec in the skill manifest (instruction-only), but the README instructs users to run a global npm install (npm install -g @membranehq/cli) or use npx. Installing a global npm package is a common pattern for CLIs, but users should review and trust the npm package before installing on sensitive systems.
Credentials
The skill declares no required env vars, no config paths, and no local credentials. It relies on Membrane's server-side connection/auth flow, which is consistent with the guidance to avoid local API keys.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It does not instruct modifying other skills or system-wide agent configs. Autonomous invocation remains enabled by default (normal for skills) but is not combined with other concerning factors.
Assessment
This skill is internally consistent: it uses the Membrane CLI to create and manage a connection to AdShares and explicitly avoids asking for local API keys. Before installing or running the commands: (1) verify you trust the @membranehq/cli npm package (review its npm page and source repo); (2) prefer running CLI installs in an isolated environment or CI runner if you are cautious about global npm installs; (3) confirm your organization’s policy about third-party services proxying API requests (Membrane will proxy requests and manage credentials server-side); and (4) during authentication, follow the browser-based flow and do not paste secrets into untrusted consoles. If you need higher assurance, ask the skill author or vendor for the exact Membrane connector ID and for documentation describing how Membrane stores and protects connection credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk971n9dhwcnywe7efs0r1me10s84ht8r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.