Chargify
v1.0.2Chargify integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chargify data.
⭐ 0· 120·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 skill is described as a Chargify integration and all runtime instructions show how to use the Membrane CLI to connect to Chargify, list actions, run actions, and proxy raw API requests. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md confines the agent to installing/using the Membrane CLI, performing login via browser, creating/listing connections, running pre-built actions, and optionally proxying requests to the Chargify API. It does not instruct reading arbitrary local files or environment variables outside the Membrane flow.
Install Mechanism
The doc instructs installing @membranehq/cli via npm (global). This is a standard package-manager install and proportional to the stated usage. There is no download-from-URL or archive extraction in the skill package itself (instruction-only).
Credentials
The skill declares no required environment variables or credentials. Authentication is delegated to Membrane (browser-based login / server-side credential management), which is consistent with the described behavior. Note that credentials are therefore held/managed by the Membrane service rather than provided directly to the skill.
Persistence & Privilege
always is false and the skill is user-invocable; model invocation is allowed (platform default). This is consistent with an integration skill that can be called to perform actions. There is no indication the skill modifies other skills or requests permanent system-wide privileges.
Assessment
This skill appears to do what it says: it relies on the Membrane CLI to access your Chargify data and does not ask for extra local credentials. Before installing, verify the @membranehq/cli npm package and Membrane service (getmembrane.com) are trustworthy for your organization because they will store and use your Chargify credentials on your behalf. Installing the CLI globally requires npm permissions on your machine. Also remember that, if the agent is allowed to invoke skills autonomously, it could run actions against your Chargify connection via Membrane — so limit agent permissions and review actions it will execute (create/update/delete) before granting broad access.Like a lobster shell, security has layers — review code before you run it.
latestvk97fee64tmc6n69c507vm0za7n8438yb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.