Prisma
v1.0.0Prisma integration. Manage data, records, and automate workflows. Use when the user wants to interact with Prisma data.
⭐ 0· 39·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 declares Prisma integration and all runtime instructions use the Membrane CLI to discover actions, run actions, or proxy requests to Prisma. Required network access and a Membrane account are consistent with that purpose.
Instruction Scope
SKILL.md confines runtime behavior to Membrane CLI commands (login, connect, action list/run, request proxy). It does not instruct reading unrelated files, accessing system config, or exfiltrating data. Headless auth uses a browser flow and user-provided code as expected.
Install Mechanism
There is no formal install spec in the skill bundle; the doc recommends running `npm install -g @membranehq/cli`. Installing a third-party npm package globally is a reasonable way to obtain the CLI but does execute code from the npm registry—verify package provenance. Using `npx` or reviewing the package source reduces risk.
Credentials
The skill requests no environment variables or credentials locally and explicitly advises letting Membrane manage credentials. This is proportionate, but be aware that authorizing a Membrane connection grants that third-party service access to your database via its connector.
Persistence & Privilege
The skill is instruction-only, has no install script, and is not marked always:true. It neither requests persistent presence nor modifies other skills or system-wide agent settings.
Assessment
This skill appears internally consistent and focused on using the Membrane CLI to interact with Prisma. Before installing or using it: 1) Verify the Membrane CLI package (@membranehq/cli) on the npm registry and its upstream repository (review recent releases and maintainers). 2) Prefer `npx @membranehq/cli` for one-off use instead of a global install, or inspect the package source before global installation. 3) Understand that creating a Membrane connection authorizes a third-party service to access your database—use a least-privilege DB account and test on non-production data first. 4) Review Membrane's privacy/security docs and retention policy for connector credentials. 5) Monitor and revoke connections when no longer needed. If you want added assurance, ask the skill author for the exact connector scopes/permissions Membrane requests when connecting to your Prisma instance.Like a lobster shell, security has layers — review code before you run it.
latestvk978msx169jhsdg4nyrys93dzx847npj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.