1S2U
v1.0.21S2U integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1S2U data.
⭐ 0· 72·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 state a 1S2U integration and the SKILL.md consistently instructs the agent to use Membrane to connect, discover actions, and run requests against the 1S2U API. Nothing requested is unrelated to that purpose.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, logging in, creating connections, listing actions, running actions, and proxying API requests. The document explicitly disclaims asking for API keys and does not instruct reading unrelated files or environment variables.
Install Mechanism
The skill is instruction-only (no install spec), but it tells the user to run `npm install -g @membranehq/cli`. Installing a global package from the public npm registry is reasonable for this use case but is an action the user should vet (source, maintainer, versions).
Credentials
The skill declares no required env vars or credentials. The guidance relies on Membrane to manage auth server-side rather than asking for keys locally, which is proportionate to the stated functionality.
Persistence & Privilege
The skill does not request always:true and has no install-time persistence. It is user-invocable and allows normal autonomous invocation (platform default) but does not request elevated privileges or modify other skills.
Assessment
This skill appears coherent, but before installing or running anything: 1) Verify the Membrane CLI package and its publisher on npm (and optionally inspect its GitHub repository) to ensure it's the official client. 2) Understand that Membrane will proxy requests to 1S2U and will see request/response data — confirm you trust that service and its privacy policy. 3) During the `membrane login` flow, review OAuth scopes and grant only what you expect. 4) If you prefer caution, run the CLI in an isolated environment (container or ephemeral VM) and avoid installing global packages on a critical host.Like a lobster shell, security has layers — review code before you run it.
latestvk972hjw23stxdv5ncedv7rsh55843sk2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.