Keen

v1.0.0

Keen integration. Manage data, records, and automate workflows. Use when the user wants to interact with Keen data.

0· 61·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 (Keen integration) match the instructions (use Membrane to talk to Keen). Minor inconsistency: registry metadata lists no required binaries, but SKILL.md instructs installing the @membranehq/cli CLI—this is reasonable for the stated purpose but should have been declared.
Instruction Scope
SKILL.md confines actions to using the Membrane CLI (login, connection list, action run, proxy requests). It does not instruct reading unrelated files or environment variables or exfiltrating data. It explicitly tells agents not to ask users for API keys.
Install Mechanism
There is no formal install spec in the registry (the skill is instruction-only), but SKILL.md recommends installing a global npm package (npm install -g @membranehq/cli) or using npx. Global npm installs modify the host and should only be done for packages you trust; the guidance to use Membrane is otherwise consistent with the skill's purpose.
Credentials
The skill requests no environment variables or credentials in the metadata and the instructions explicitly avoid asking for API keys (Membrane handles auth). This is proportionate for a connector/proxy integration.
Persistence & Privilege
always is false and the skill does not request system-wide persistence or modify other skills. Autonomous invocation is allowed (default) but not combined with elevated privileges or broad credential requests.
Assessment
This skill delegates all network and credential handling to the Membrane service and its CLI. Before installing or using it: (1) verify the @membranehq/cli package and getmembrane.com are the official Membrane project (check the npm package owner, repository, and homepage), (2) prefer running actions with npx rather than doing a global npm install if you want to avoid modifying your system PATH, (3) understand that Membrane will hold the Keen credentials and proxy requests — only use if you trust that service, and (4) be cautious when allowing autonomous agents to call connectors (monitor activity and limit agent permissions if possible). If you need stronger assurance, request an explicit install spec or signed package info from the skill author.

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

latestvk974pnmbvhb8ebsnt4v7s9xach84bzqg

License

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

Comments