Sitespeakai
v1.0.2SiteSpeakAI integration. Manage Organizations. Use when the user wants to interact with SiteSpeakAI data.
⭐ 0· 105·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
The name/description (SiteSpeakAI integration) match the instructions: all actions are performed via the Membrane CLI and Membrane connections to SiteSpeakAI. Nothing in the SKILL.md asks for unrelated credentials, binaries, or config paths.
Instruction Scope
The runtime instructions are narrowly scoped to installing and using the Membrane CLI, creating a connector, running Membrane actions, and optionally proxying raw API requests through Membrane. Important privacy note: proxying and actions go through Membrane servers (they handle auth and refresh), so request/response payloads and metadata will transit Membrane — the user should be comfortable with that.
Install Mechanism
No bundled code or downloads in the skill itself; the SKILL.md recommends installing @membranehq/cli via npm (global install). Using an npm package is reasonable for a CLI, but users may prefer npx to avoid a global install or to verify the package source first.
Credentials
The skill declares no env vars, no config paths, and no credentials. The instructions explicitly direct you to let Membrane manage credentials rather than asking for API keys locally — this matches the stated purpose.
Persistence & Privilege
Skill is instruction-only, has no 'always: true' flag, and requests no persistent elevated privileges. Autonomous invocation is allowed (platform default) and is not by itself a concern here.
Assessment
This skill is internally consistent: it tells you to install and use the Membrane CLI to connect to SiteSpeakAI and does not ask for unrelated secrets. Before installing: (1) verify the @membranehq/cli package and publisher (use npx/@latest if you prefer not to install globally); (2) understand that Membrane acts as a proxy and will see request/response data and tokens — review Membrane's privacy/security posture; (3) perform browser-based login only on trusted devices and revoke the connection in Membrane if you no longer need it; (4) do not provide unrelated credentials to the skill. If you need stricter isolation, consider running the CLI in a container or temporary VM.Like a lobster shell, security has layers — review code before you run it.
latestvk975jeqhrh92bssfahftt4efp9842g05
License
MIT-0
Free to use, modify, and redistribute. No attribution required.