Addsearch

v1.0.2

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

0· 64·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
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill claims to integrate with AddSearch and all runtime instructions use the Membrane CLI and Membrane proxy to interact with AddSearch. Required resources (network access and a Membrane account) match the stated purpose.
Instruction Scope
SKILL.md stays on-topic: it instructs installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests. It does not instruct reading unrelated files, harvesting environment variables, or sending data to unexpected endpoints. It does rely on user/browser-based authentication via Membrane.
Install Mechanism
The skill has no formal install spec (instruction-only), but the README instructs installing a global npm package (@membranehq/cli). Asking users to install a third-party global npm CLI is expected for this integration but carries the usual risks of running third-party packages; the skill itself does not auto-install anything.
Credentials
No environment variables, credentials, or config paths are requested by the skill. Authentication is delegated to Membrane (browser-based login / connection flow), which is proportionate to the goal of accessing AddSearch.
Persistence & Privilege
The skill is not always-enabled and does not request persistent system privileges or modify other skills. The default ability for the agent to invoke the skill autonomously is present but not combined with other risky flags.
Assessment
This skill is coherent: it delegates AddSearch access to the Membrane service and asks you to install and use the Membrane CLI. Before installing or using it, verify you trust Membrane (getmembrane.com / @membranehq/cli), understand that installing a global npm package runs third-party code, and be comfortable with the browser-based login flow (Membrane will hold credentials server-side). If you require on-premises control of credentials, this SaaS-mediated workflow may not meet your security requirements.

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

latestvk975qxjsdtp49r2v6g8v1m34gh842te3

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments