Sessions
v1.0.0Sessions integration. Manage Sessions, Persons, Organizations, Notes, Files. Use when the user wants to interact with Sessions data.
⭐ 0· 8·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the instructions: the SKILL.md explains how to use the Membrane CLI to manage Sessions, Persons, Organizations, Notes and Files. There are no unrelated environment variables, binaries, or config paths requested that would be inconsistent with a Sessions integration.
Instruction Scope
All runtime instructions are limited to running the Membrane CLI (npx @membranehq/cli@latest) to discover actions, create connections, run actions, or proxy requests to the Sessions API. The doc references the credentials file (~/.membrane/credentials.json) which the CLI will create/use; instructions do not ask the agent to read arbitrary unrelated files, but the workflow will result in local storage of tokens.
Install Mechanism
No formal install spec is present (instruction-only), but the workflow relies on npx fetching and executing @membranehq/cli@latest from the npm registry at runtime. Using npx @latest executes code downloaded from npm each time (supply-chain risk compared with a pinned release), but this is expected for a CLI-driven integration.
Credentials
The skill declares no required environment variables or unrelated credentials. It does require a Membrane account and the CLI will create/store credentials in ~/.membrane/credentials.json; that is proportional for a delegated auth flow but is worth noting because secrets are stored locally and Membrane will broker access to the target Sessions service.
Persistence & Privilege
The skill is not always-enabled, includes no install that writes persistent system-wide config, and does not request elevated privileges. The only persistence is the Membrane CLI storing credentials in the user's home directory (normal for CLI auth flows).
Assessment
This skill appears to do what it claims: it delegates Sessions interactions to the Membrane CLI and does not request unrelated credentials. Before installing/use, consider: 1) you'll need a Membrane account and the CLI will store tokens in ~/.membrane/credentials.json; review that file and its access. 2) the instructions use npx @membranehq/cli@latest (downloads and runs code from npm each time) — if you prefer lower supply-chain risk, run a pinned version (e.g. @membranehq/cli@x.y.z) or inspect the package first. 3) the agent will run shell commands and may open browser auth flows; if you allow autonomous invocation, these commands could be executed without further prompts. If you are unsure, run the shown npx commands yourself in a controlled environment to validate behavior before granting the agent access.Like a lobster shell, security has layers — review code before you run it.
latestvk97fv0852d4fcjjceckfv1ekas848akv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.