Chargent
v1.0.0Chargent integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chargent data.
⭐ 0· 27·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 match the instructions: all steps are about installing/using the Membrane CLI to connect to Chargent, list actions, run actions, or proxy requests. Nothing requested is unrelated to a Chargent integration.
Instruction Scope
Runtime instructions are scoped to installing Membrane, logging in, creating or listing connections, discovering actions, running actions, and proxying requests to Chargent. The instructions do not direct the agent to read unrelated files, harvest environment variables, or contact unexpected endpoints.
Install Mechanism
Install-only guidance is an npm global install of @membranehq/cli (and npx usage). This is expected for a CLI but carries the normal risks of globally installing an npm package (code written to disk and executed). The instruction references official-sounding sources (getmembrane.com and a GitHub org) rather than arbitrary download URLs.
Credentials
The skill declares no required environment variables or credentials. Authentication is delegated to Membrane via an interactive login/connection flow, which is appropriate and avoids asking for local API keys.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and has no declared config-path requirements. Autonomous invocation is allowed (platform default) but there are no indications of overbroad persistent privileges.
Assessment
This skill looks coherent and focused: it uses the Membrane CLI to talk to Chargent and does not request unrelated secrets. Before installing, verify you trust the Membrane project (review the npm package and the GitHub repo), be aware that npm -g installs will write and run code on your machine, and review the permissions/scope you grant when authorizing the Chargent connection in Membrane (the proxy means Membrane will see the API traffic). If you prefer not to install a global CLI, you can use npx for one-off calls or run the CLI in a controlled environment/sandbox.Like a lobster shell, security has layers — review code before you run it.
latestvk974hf34x1we9n007raj3v3rdn846g39
License
MIT-0
Free to use, modify, and redistribute. No attribution required.