Stripe Identity
v1.0.2Stripe Identity integration. Manage data, records, and automate workflows. Use when the user wants to interact with Stripe Identity data.
⭐ 0· 60·0 current·0 all-time
byVlad Ursul@gora050
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 (Stripe Identity integration) align with the instructions: installing/using the Membrane CLI, creating a connector, listing/running actions, and proxying requests to the Stripe Identity API via Membrane. There are no unrelated required env vars, binaries, or config paths.
Instruction Scope
SKILL.md gives concrete CLI steps (install CLI, login, connect, list/run actions, proxy requests). It does not instruct reading arbitrary local files or environment variables beyond the interactive login, and it explicitly tells integrators not to ask users for API keys. It does rely on network access and a Membrane account, which is appropriate for the stated purpose.
Install Mechanism
This is an instruction-only skill (no install spec), but it instructs installing @membranehq/cli globally via npm. That is a common, traceable install mechanism (npm registry) but carries the usual moderate risk of installing code from a package registry—users should verify the package source/version before global installation.
Credentials
No environment variables, secrets, or config paths are requested. The skill delegates credential management to Membrane (browser-based login), which is consistent with the workflow. The only external requirement is a Membrane account.
Persistence & Privilege
The skill is not marked always:true and does not request persistent or elevated system privileges. It does not modify other skills' configs. Autonomous invocation is allowed (platform default) but is not combined with other concerning flags here.
Assessment
This skill appears coherent and does what it says: use Membrane to talk to Stripe Identity. Before installing/use: 1) Verify and trust the @membranehq/cli package (check publisher, npm page, and GitHub repo) before running npm -g. 2) Understand that Membrane will hold and proxy Stripe credentials server-side—only proceed if you trust that service and review the connector permissions. 3) Use least-privilege Stripe/test accounts when possible and avoid pasting raw keys into chat. 4) If you are concerned about autonomous agent actions, limit agent permissions or require explicit invocation for operations that proxy requests to external APIs.Like a lobster shell, security has layers — review code before you run it.
latestvk97bhsmqbmt18tr3dwejraj2th843e8e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.