Screensteps
v1.0.0ScreenSteps integration. Manage data, records, and automate workflows. Use when the user wants to interact with ScreenSteps data.
⭐ 0· 60·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 name/description (ScreenSteps integration) matches the instructions: the SKILL.md tells the agent to use the Membrane CLI to connect to ScreenSteps. There are no unrelated required binaries or environment variables declared.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, logging in via browser, creating a connection, listing actions, running actions, and proxying requests to ScreenSteps through Membrane. This is within scope, but proxy functionality means the CLI (and Membrane service) can forward arbitrary requests to the ScreenSteps API — you must trust that service and the account you authorize.
Install Mechanism
There is no registry install spec; however SKILL.md instructs installing @membranehq/cli via `npm install -g`. This is a public npm package (moderate risk). Installing a global npm package is a manual action that writes code to disk and requires you to trust the package and its publisher.
Credentials
No environment variables or credentials are requested by the skill. Authentication is performed by Membrane's login flow (browser-based) and connection creation, which avoids local secrets but shifts trust to Membrane's service.
Persistence & Privilege
Skill does not request always:true or other elevated persistent privileges. It is user-invocable and allows normal autonomous invocation (platform default). The skill does not modify other skill configs or request system-wide settings.
Assessment
This skill is coherent but requires you to install and trust the Membrane CLI/service and to authorize ScreenSteps access in your browser. Before proceeding: (1) verify the @membranehq/cli package on npm and prefer running via npx if you want to avoid a global install; (2) review the permissions and account you give during the Membrane login/connection flow — the connection lets Membrane proxy arbitrary requests to your ScreenSteps data; (3) be prepared to revoke the connection from Membrane or ScreenSteps if you stop trusting it; and (4) only install the CLI from the official source (check package maintainer, repository, and checksums) if you are comfortable trusting that third-party service.Like a lobster shell, security has layers — review code before you run it.
latestvk977dzptm17k88449y2924szad84566m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.