Superdocu
v1.0.2Superdocu integration. Manage Documents, Users, Groups, Templates. Use when the user wants to interact with Superdocu data.
⭐ 0· 91·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
medium confidencePurpose & Capability
The name/description (Superdocu integration) match the SKILL.md: all actions are performed via the Membrane CLI and Superdocu API. Minor inconsistency: the skill does not declare required local binaries (Node/npm or the membrane CLI) even though the instructions tell the user to install and run them.
Instruction Scope
Runtime instructions are narrowly focused on using the Membrane CLI to list/connect/run actions and proxy requests to the Superdocu API. The SKILL.md does not instruct the agent to read unrelated files, access unrelated environment variables, or exfiltrate data to unexpected endpoints.
Install Mechanism
There is no formal install spec, but SKILL.md instructs installing @membranehq/cli via npm (global install) and suggests running npx @membranehq/cli@latest. Installing/running packages from the public npm registry is normal but carries the usual risk of executing remote code; consider pinning versions or reviewing the package source before running.
Credentials
The skill requests no environment variables or secrets and explicitly instructs to avoid asking users for API keys. Authentication is delegated to Membrane (connection workflow), which is appropriate and proportionate for this integration.
Persistence & Privilege
The skill is not always-enabled and is user-invocable. It does not request system-wide configuration changes or persistent privileges beyond normal CLI installation.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to manage Superdocu data. Before installing, note that SKILL.md expects you to install/run the @membranehq/cli package (via npm or npx) — that will download and execute code from the npm registry. Verify you have Node/npm installed, review the @membranehq/cli package (or pin to a specific version) and the Membrane project's source/reputation, and confirm the Membrane connection permissions so you understand what Superdocu data the connection can access. Avoid pasting API keys into chat; follow the documented browser-based connection flow and verify any network requests are going to official Membrane/Superdocu endpoints.Like a lobster shell, security has layers — review code before you run it.
latestvk9753b2qx6yhg070pnkjct8vg1843cdr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.