Emelia
v1.0.2Emelia integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Emelia data.
⭐ 0· 151·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
The skill declares no required binaries or env vars in the registry metadata, but the SKILL.md clearly expects the Membrane CLI to be installed and network access to a Membrane account. Requiring the Membrane CLI is appropriate for an Emelia integration, but the metadata omission is a minor mismatch.
Instruction Scope
Instructions are scoped to discovering connections, listing actions, running actions, and proxying requests to Emelia via the Membrane CLI. They do not instruct reading unrelated local files or exfiltrating arbitrary system data and explicitly advise against asking the user for API keys.
Install Mechanism
There is no formal install spec in the registry; instead SKILL.md instructs users to run `npm install -g @membranehq/cli`. Installing a public npm CLI is a normal way to get the required tooling but does involve fetching third-party code from the npm registry — verify the package source and maintainers before installing globally.
Credentials
The skill declares no required environment variables or credentials and directs authentication to Membrane's browser-based flow. This is proportionate for a connector that delegates auth to Membrane and avoids asking the user for direct API keys.
Persistence & Privilege
The skill is instruction-only and does not request always:true or any elevated agent-wide privileges. The Membrane CLI itself will store connection tokens/config locally as part of normal operation; that is expected but separate from the skill's metadata.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to manage Emelia resources. Before installing or running commands: (1) verify the `@membranehq/cli` package on npm (publisher, repository URL, recent releases) or install it in a controlled environment/container rather than globally on a production machine; (2) expect a browser-based OAuth flow (do not paste secrets into chat); (3) review any JSON returned by `membrane` commands before acting on it; and (4) note the registry metadata didn’t list the Membrane CLI as a required binary — treat that as a documentation mismatch, not a functional blocker.Like a lobster shell, security has layers — review code before you run it.
latestvk977d5bndt3jzqktfmmr04afv9843nbf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.