Mediatoolkit

v1.0.2

Mediatoolkit integration. Manage Alerts, Users, Dashboards, Reports. Use when the user wants to interact with Mediatoolkit data.

0· 104·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 (Mediatoolkit integration) match the instructions (use Membrane CLI to discover and run Mediatoolkit actions and proxy API requests). Required capabilities (network and a Membrane account) are consistent with the stated purpose.
Instruction Scope
SKILL.md limits runtime behavior to installing/using the Membrane CLI, running search/action/connect/request commands, and following browser-based login flows. It does not instruct reading arbitrary host files, environment variables, or sending data to unexpected endpoints. It explicitly advises against asking the user for API keys.
Install Mechanism
No install spec in registry, but SKILL.md recommends 'npm install -g @membranehq/cli' (and also shows npx usage). Installing a global npm package is a reasonable install method for a CLI but carries the usual moderate risk of running code from the npm registry and possible postinstall scripts — verify the package and publisher before global installation or prefer npx to avoid persisting a global binary.
Credentials
The skill requests no environment variables, no config paths, and no secrets in the metadata. Authentication is handled via Membrane interactive login flows, which is proportionate to integrating a third-party API.
Persistence & Privilege
The skill is not always-enabled and needs explicit invocation. It does not request elevated platform privileges or attempt to modify other skills or system-wide settings in the instructions.
Assessment
This skill is coherent but relies on the third-party Membrane CLI/service. Before installing: (1) verify the npm package (@membranehq/cli) and its repository (review recent commits and publisher), (2) prefer 'npx @membranehq/cli@latest' if you want to avoid a global install, (3) run the CLI in an environment you trust (or a container) because it will open browser-based auth flows and Membrane will proxy/hold connection credentials, and (4) review Membrane's privacy/security documentation to understand how connection tokens and proxied requests are stored and handled.

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

latestvk9797a0bkp9g340mz1e06139j1843t3z

License

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

Comments