Successeve
v1.0.2Successeve integration. Manage Organizations, Users. Use when the user wants to interact with Successeve data.
⭐ 0· 124·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
Name/description match the instructions: the SKILL.md explains how to use Membrane to manage Successeve Organizations and Users. Nothing in the instructions requests unrelated capabilities or credentials.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, logging in, creating connections, listing/running actions, and proxying API requests via Membrane. This stays within the stated purpose, but proxying means your Successeve requests and data will transit Membrane's service—a privacy/third‑party data flow consideration the user should understand.
Install Mechanism
No registry install spec is embedded (skill is instruction-only) but the SKILL.md instructs running `npm install -g @membranehq/cli` (or using npx). Installing a global third‑party CLI is a reasonable requirement for this integration but carries the usual supply‑chain/privacy considerations—verify package identity and prefer npx if you want to avoid a global install.
Credentials
The skill declares no environment variables, secrets, or config paths. It relies on Membrane to handle authentication server‑side; this is proportionate but implies Membrane will hold/access your Successeve credentials/tokens.
Persistence & Privilege
The skill does not request persistent privileges (always is false), does not modify other skills or system configurations, and is user‑invocable/autonomous invocation is default platform behavior.
Assessment
This skill is coherent but depends on a third‑party service (Membrane) and a third‑party CLI. Before installing or using it: 1) Confirm you trust getmembrane.com/@membranehq and review the @membranehq/cli package (source, maintainer, and version). 2) Understand that API requests and tokens will be proxied through Membrane—don’t use it for data you cannot share with that provider. 3) If you prefer less system impact, use npx to run the CLI without a global install. 4) After use, audit and revoke any Membrane connections in your account if you no longer want them active.Like a lobster shell, security has layers — review code before you run it.
latestvk97b835hkafjd1sf0zc37q71ax8429c1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.