Swoogo
v1.0.0Swoogo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Swoogo data.
⭐ 0· 25·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 (Swoogo integration) matches the instructions: all actions use the Membrane CLI to discover and run Swoogo-related actions or proxy requests to the Swoogo API. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md instructs installing and using the Membrane CLI, logging in via browser, creating connections, listing actions, running actions, and proxying requests — all within the stated Swoogo integration scope. It does not instruct reading unrelated files, harvesting environment variables, or sending data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec), but it tells the user to run an npm global install (npm install -g @membranehq/cli). Installing a public npm package is common and traceable, but it does write code to the system (global npm install) — a moderate operational consideration rather than an incoherence.
Credentials
The skill requests no environment variables or secrets. It relies on the Membrane login flow (browser-based OAuth-like flow) to obtain credentials, and explicitly advises not to ask users for API keys. The requested access is proportionate to the stated integration purpose.
Persistence & Privilege
always:false and normal model invocation are used. The skill does not request persistent presence or modify other skills/system-wide settings. Autonomous invocation is allowed (platform default) but not coupled with broad/unjustified privileges.
Assessment
This skill appears coherent and safe in design, but before installing: (1) verify you trust the @membranehq npm package and the publisher (global npm installs add code to your system), (2) be prepared to authenticate via a browser (Membrane handles tokens server-side), (3) review Membrane/Swoogo OAuth scopes and privacy if the connection will access sensitive event or attendee data, and (4) if you operate in restricted or CI/headless environments, follow the documented headless login flow and confirm it meets your security policies.Like a lobster shell, security has layers — review code before you run it.
latestvk97bgmvpn7tyfy7avpsemhjh0h846xwe
License
MIT-0
Free to use, modify, and redistribute. No attribution required.