Woopra
v1.0.2Woopra integration. Manage data, records, and automate workflows. Use when the user wants to interact with Woopra data.
⭐ 0· 80·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
high confidencePurpose & Capability
The name/description (Woopra integration) matches the instructions (use Membrane CLI to connect to Woopra). Required capabilities (network access, a Membrane account, and the Membrane CLI) are coherent with the stated purpose; there are no unrelated environment variables or permissions requested.
Instruction Scope
SKILL.md restricts runtime actions to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to the Woopra API. It explicitly avoids asking for raw API keys. The instructions do require browser-based authentication (standard for OAuth flows) and sending data through Membrane's service, which is expected for this integration.
Install Mechanism
The skill has no formal install spec, but the instructions recommend a global npm install (npm install -g @membranehq/cli). Installing a third-party CLI globally executes and writes third-party code to disk; this is normal for CLI usage but warrants verifying the package source (npm page, repository, publisher) before installation or using npx/local installs if preferred.
Credentials
No environment variables, credentials, or config paths are required by the skill itself. Authentication is delegated to Membrane (browser-based OAuth), which aligns with the guidance in SKILL.md.
Persistence & Privilege
The skill does not request always:true or system-wide configuration changes. It is user-invocable and can be invoked autonomously per platform defaults; there are no elevated persistence or cross-skill configuration modifications in the instructions.
Assessment
This skill appears coherent, but before installing/use: 1) Verify you trust Membrane and the @membranehq/cli package (check the npm page, GitHub repo, and publisher). 2) Be aware that requests and data will flow through Membrane's servers—don't proxy highly sensitive data unless you accept that data handling. 3) Prefer npx or a local install if you don't want a global CLI installed. 4) Use a test/account-limited Woopra or Membrane connection first and revoke the connection when finished. 5) If unsure, inspect the Membrane CLI source or consult your security/compliance team.Like a lobster shell, security has layers — review code before you run it.
latestvk978tpbk48excvqrbgt8pwt961842n01
License
MIT-0
Free to use, modify, and redistribute. No attribution required.