Waitlist

v1.0.2

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

0· 101·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 Waitlist and its SKILL.md exclusively instructs using the Membrane CLI and Membrane-hosted connectors/proxy to access Waitlist — this matches the stated purpose.
Instruction Scope
Instructions focus on installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests. They do not instruct reading unrelated files, accessing unrelated environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec) but it tells the user to run `npm install -g @membranehq/cli`. Installing a global npm package is expected for a CLI workflow but carries the usual supply-chain/trust considerations — verify the package name/maintainer before installing, and avoid installing in restricted/shared systems without review.
Credentials
The skill does not request environment variables, secrets, or system config paths. It explicitly advises against asking users for API keys and instead uses Membrane-managed connections, which is proportionate and appropriate.
Persistence & Privilege
The skill does not request always-on presence, does not modify other skills, and does not request elevated system privileges. Autonomous invocation is permitted but is the platform default and not elevated by this skill.
Assessment
This skill appears to do only what it says: it uses the Membrane CLI to connect to Waitlist. Before installing the CLI (npm install -g @membranehq/cli), verify the npm package and maintainer (@membranehq) and ensure you trust installing a global npm package on the machine (it may require admin rights). Expect browser-based authentication (OAuth/connection flow) and network access to Membrane/Waitlist. The skill does not ask for raw API keys or local secrets. If you plan to run this in a CI or shared environment, prefer scoped installs or review the CLI's code/repository and Membrane's privacy/security docs first.

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

latestvk97cdsh9cwrqcdmnce0awysag9843qse

License

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

Comments