Warpwire
v1.0.0Warpwire integration. Manage data, records, and automate workflows. Use when the user wants to interact with Warpwire data.
⭐ 0· 28·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 name/description (Warpwire integration) matches the instructions which use Membrane to connect to Warpwire. All declared capabilities (discover actions, run actions, proxy requests) are coherent with interacting with Warpwire data.
Instruction Scope
SKILL.md only instructs the agent to install and use the Membrane CLI, perform browser-based login, list connections/actions, run actions, or proxy API calls. It does not request unrelated files, system paths, or additional environment variables.
Install Mechanism
There is no automatic install spec in the skill bundle (instruction-only), but the instructions ask the user to run `npm install -g @membranehq/cli` or use `npx`. Installing a global npm CLI is a reasonable approach but requires trusting the npm package publisher and modifies the system environment.
Credentials
The skill declares no required env vars or credentials and explicitly says Membrane handles auth. This is proportionate to the purpose, but it means Warpwire credentials will be managed/stored by the Membrane service — users must trust that service with their Warpwire auth.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide agent settings, and has no config path requirements. Normal autonomous invocation is allowed (platform default).
Assessment
This skill appears coherent, but before installing or using it: (1) verify the @membranehq/cli npm package and its publisher (check the package page and the GitHub repo referenced) to ensure authenticity; (2) be aware that global npm installs change your system PATH and may require elevated privileges — consider using npx or a containerized environment if you prefer less system impact; (3) understand that Membrane will hold and refresh Warpwire credentials on your behalf — review Membrane's privacy/security docs and terms before delegating access; (4) if you need stronger isolation, avoid global install and run the CLI in a controlled environment or CI with minimal privileges.Like a lobster shell, security has layers — review code before you run it.
latestvk972xzxdgdt7g4twa15mjnwv4x846c1w
License
MIT-0
Free to use, modify, and redistribute. No attribution required.