Kotive
v1.0.0Kotive integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kotive data.
⭐ 0· 54·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
medium confidencePurpose & Capability
The skill's name/description (Kotive integration) align with the instructions (use Membrane to access Kotive). However the registry metadata lists no required binaries or env vars even though SKILL.md clearly expects the Membrane CLI (and implicitly npm or npx to install/run it). This is likely an oversight in metadata rather than malicious behavior.
Instruction Scope
SKILL.md stays within the stated purpose: it instructs using the Membrane CLI to discover actions, run actions, and proxy arbitrary Kotive API calls. It does not ask to read unrelated files or request unrelated credentials. Note: the proxy command allows arbitrary API requests to Kotive through Membrane (expected for this integration) — review any proxied paths you run.
Install Mechanism
There is no automated install spec in the registry; SKILL.md recommends installing @membranehq/cli via npm (a public npm package). Installing a global npm CLI is a standard approach but is not declared in the metadata; the package comes from the public registry (moderate risk if automated).
Credentials
The skill requests no environment variables or local secrets. Authentication is delegated to Membrane (browser-based login), so the skill does not ask for API keys or tokens directly. This is proportionate to the stated purpose, but it does rely on trusting Membrane to manage Kotive credentials.
Persistence & Privilege
The skill does not request always-on presence, nor does it indicate modifying other skills or system-wide settings. It is instruction-only and relies on an external CLI run by the user/agent.
Assessment
This skill uses the Membrane CLI to access Kotive and delegates authentication to Membrane (you sign in via browser). Before installing/using it: 1) be prepared to install a global npm package or use npx; the registry metadata omits this requirement. 2) Understand that Membrane will hold and refresh Kotive credentials on your behalf—only proceed if you trust the Membrane service. 3) When invoking proxy commands (membrane request), double-check paths and payloads to avoid unintentionally exposing or modifying data. If you want higher assurance, ask the publisher to update the registry metadata to declare the required CLI/npm dependency.Like a lobster shell, security has layers — review code before you run it.
latestvk97bd69s4rbdhheqg0ea9vczvn848q9a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.