Slope
v1.0.2Slope integration. Manage data, records, and automate workflows. Use when the user wants to interact with Slope data.
⭐ 0· 71·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
high confidencePurpose & Capability
The skill claims to integrate with Slope and all runtime instructions use the Membrane CLI to manage Slope connections, run actions, and proxy API requests. Asking the user to authenticate via Membrane and to use membrane action/request is appropriate for the stated purpose.
Instruction Scope
SKILL.md stays on-topic: it instructs installing the Membrane CLI, performing login, creating connections, listing actions, running actions, and proxying requests. It does not ask the agent to read unrelated files, harvest environment variables, or transmit data to unexpected endpoints beyond Membrane/Slope.
Install Mechanism
The skill is instruction-only (no install spec), but it tells the user to install the @membranehq/cli via npm (global install) or use npx. Installing a global npm package changes the system environment and runs code from the npm registry; this is expected for a CLI-based integration but carries the usual risk of executing third-party code. The metadata did not declare required binaries (npm/npx/node), which is a minor mismatch.
Credentials
No environment variables or credentials are requested by the skill; it explicitly recommends creating a Membrane connection rather than asking the user for API keys. This is proportionate to the stated functionality.
Persistence & Privilege
The skill does not request always:true and has no install-time persistence. It relies on the Membrane service for auth and does not modify other skills or system-wide agent configuration in the instructions.
Assessment
This skill is coherent for interacting with Slope via the Membrane CLI, but before installing: 1) verify the @membranehq/cli package and its GitHub/npm pages to ensure you trust the publisher; 2) prefer using npx for one-off use instead of a global npm install if you want less system impact; 3) be aware membrane request will proxy arbitrary API paths (it can send whatever you ask through Membrane), so avoid passing sensitive local data unless you trust the Membrane service and connection; 4) note the SKILL.md expects npm/npx/node even though the metadata doesn't declare required binaries — ensure your environment meets those prerequisites and sandbox the CLI install if desired.Like a lobster shell, security has layers — review code before you run it.
latestvk97egcdv33eedt8318aw4t4rpn843a8h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.