Peaka
v1.0.2Peaka integration. Manage Organizations, Pipelines, Users, Filters, Files, Notes and more. Use when the user wants to interact with Peaka data.
⭐ 0· 115·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 (Peaka integration) match the runtime instructions: the skill directs use of the Membrane CLI to connect to Peaka, discover actions, run actions, or proxy requests. Required network access and a Membrane account are expected for this purpose.
Instruction Scope
SKILL.md confines itself to installing/using the Membrane CLI, logging in, creating/locating a Peaka connector, listing/running actions, and using Membrane's proxy. It explicitly advises against requesting API keys from users. No instructions read unrelated files, request unrelated environment variables, or send data to unexpected endpoints.
Install Mechanism
The install guidance recommends installing @membranehq/cli globally via npm (or using npx in examples). Installing an npm package is a reasonable and common approach for a CLI, but global npm installs run third-party code on the user's machine — verify the package name, publisher, and version before installing, or prefer npx to avoid a global install.
Credentials
The skill declares no required environment variables, no config paths, and no credentials. It relies on Membrane to manage auth, which is proportionate to the stated goal. There are no requests for unrelated secrets or multiple external credentials.
Persistence & Privilege
No install spec, no code written by the skill, and always:false. The skill is instruction-only and does not request persistent agent privileges or modify other skills' configurations.
Assessment
This skill is coherent and uses the Membrane CLI to access Peaka. Before installing or running commands: (1) confirm you trust the @membranehq/cli npm package and the getmembrane.com service (they will proxy requests and hold connector credentials); (2) prefer using npx for one-off commands to avoid a global npm install; (3) review the Membrane CLI package version and publisher on the npm registry or GitHub repo; (4) be aware that Membrane will handle authentication and thus will see proxied request data — only proceed if you are comfortable with that data flow.Like a lobster shell, security has layers — review code before you run it.
latestvk97erddwms2cy3czgcnpvy9mb5842q1d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.