Privyid

v1.0.2

PrivyID integration. Manage data, records, and automate workflows. Use when the user wants to interact with PrivyID data.

0· 81·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name and description (PrivyID integration) match the instructions: it delegates to the Membrane CLI to connect, run actions, and proxy requests to PrivyID. It does not request unrelated credentials or services.
Instruction Scope
SKILL.md confines the agent to installing/using the Membrane CLI, performing login via browser, creating connections, listing actions, running actions, and proxying API calls. It does not instruct reading local files, environment variables, or sending data to unexpected endpoints beyond Membrane/PrivyID.
Install Mechanism
There is no built-in install spec; the doc suggests a user-run npm global install of @membranehq/cli. This is appropriate for a CLI-based integration but installing a third-party npm package globally executes code from the package registry — users should ensure they trust @membranehq/cli and review its source/permissions before installing.
Credentials
The skill declares no required env vars or credentials. Authentication is handled via Membrane's login flow (browser-based), which is proportional to the stated purpose. There are no requests for unrelated secrets or config paths.
Persistence & Privilege
always:false and normal autonomous invocation are used. The skill does not request persistent system-wide changes or modify other skills' configs. No elevated privileges are requested in the instructions.
Assessment
This skill is internally consistent: it relies on the Membrane CLI to talk to PrivyID and does not ask for local API keys. Before installing/using it, verify you trust the Membrane service and the @membranehq/cli package (review its repository and permissions), be aware the login flow grants Membrane access to your PrivyID connection, and avoid installing third-party global npm packages on sensitive production machines unless reviewed.

Like a lobster shell, security has layers — review code before you run it.

latestvk9718jq5fs6eycccbxdx09t4ad842yhh

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments