Mem
v1.0.2Mem integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Mem data.
⭐ 0· 146·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 name/description (Mem integration) matches the instructions (use Membrane CLI to manage Mem resources). Required network access and a Membrane account are appropriate for this integration.
Instruction Scope
SKILL.md confines actions to installing/using the Membrane CLI, creating/listing connections, running connector actions, and proxying requests to the Mem API. It does not instruct reading unrelated local files, accessing unrelated env vars, or exfiltrating data to unexpected endpoints. The proxy capability allows calling arbitrary Mem endpoints, which is expected for a connector.
Install Mechanism
This is an instruction-only skill with no install spec. It tells the user to install @membranehq/cli from npm (npm install -g or npx). Installing a third-party global CLI is a standard but moderately privileged step — the package will be downloaded from the public npm registry, so verify the package and source before installing.
Credentials
The skill declares no required env vars or credentials and explicitly advises letting Membrane handle auth. No unrelated credentials, config paths, or secret-exposing steps are requested.
Persistence & Privilege
Skill is not always-enabled and has no special persistence requirements. It does not request modification of other skills or system-wide settings. Note: autonomous invocation (model invoking the skill) is allowed by platform default but is not combined here with broad credentials or other red flags.
Assessment
This skill appears coherent for interacting with Mem through the Membrane CLI. Before installing/using it: (1) verify the @membranehq/cli package and its publisher on npm/GitHub; (2) be aware the CLI runs network requests and may proxy arbitrary Mem API calls once you create a connection — review the Membrane connection permissions and what accounts/services are connected; (3) perform the browser-based login yourself (do not paste secrets into chat); and (4) if you want stricter control, avoid installing the global CLI and instead run it in an isolated environment or container.Like a lobster shell, security has layers — review code before you run it.
latestvk9775rmzd68y18r3g3xsw5mbf9842866
License
MIT-0
Free to use, modify, and redistribute. No attribution required.