Supportivekoala

v1.0.2

Supportivekoala integration. Manage Organizations, Pipelines, Users, Filters, Projects. Use when the user wants to interact with Supportivekoala data.

0· 99·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
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description describe a Supportivekoala integration and the SKILL.md only requires the Membrane CLI, network access, and a Membrane account — all coherent with the stated purpose. No unrelated services, credentials, or binaries are requested.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, logging in, creating connections, listing and running actions, and proxying API requests through Membrane. The guide does not direct the agent to read unrelated files, harvest secrets, or post data to third-party endpoints outside of Membrane/Supportivekoala.
Install Mechanism
There is no automated install spec in the registry; the SKILL.md recommends the public npm package '@membranehq/cli' (npm install -g). That's a typical installation path but carries the usual considerations of installing global npm packages — verify package authenticity and trust the publisher before running.
Credentials
The skill declares no required environment variables or credentials. Authentication is handled via Membrane (browser login / headless flow), so it does not ask for local API keys or secrets — this is proportionate to its function.
Persistence & Privilege
The skill is not always-enabled and does not request special platform privileges. The only persistence impact described is the normal Membrane CLI login (local token storage / browser auth), which is expected behavior for a CLI-based integration.
Assessment
This skill appears coherent and uses the Membrane CLI as intended. Before installing/using it: (1) verify the '@membranehq/cli' package on npm and its GitHub repo to confirm publisher authenticity; (2) review Membrane's privacy and authorization flows so you know what data and scopes the connector will get; (3) be aware that 'npm install -g' modifies your system environment — run it only on trusted machines; (4) do not provide unrelated credentials to this skill; and (5) if you plan to let an autonomous agent invoke the skill, review what actions the agent may run through the connection (Membrane will proxy requests with the connector's privileges).

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

latestvk971fxbma3jggyth5gdn3ep2bs842x4r

License

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

Comments