Paykickstart
v1.0.2Paykickstart integration. Manage Campaigns. Use when the user wants to interact with Paykickstart data.
⭐ 0· 119·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
Name/description (Paykickstart integration) align with the instructions: the SKILL.md consistently describes using Membrane to connect to PayKickstart, discover actions, run actions, and proxy API requests. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, creating a Membrane connection, listing/running actions, and proxying requests. One notable behavior: the skill explicitly routes API calls through Membrane, meaning request payloads and responses will traverse Membrane's service — this is expected for a proxy-based integration but is worth the user's awareness.
Install Mechanism
No registry install spec is provided (instruction-only). The SKILL.md suggests installing @membranehq/cli globally via npm (or using npx). This is proportionate for a CLI-based integration but does require the user to run npm -g (global install) or npx, which has standard privilege and supply-chain implications to consider.
Credentials
The skill requests no environment variables, no local credentials, and no config paths. Authentication is delegated to Membrane via an interactive login flow, which is coherent with the stated approach of not handling API keys locally.
Persistence & Privilege
The skill does not request always:true, does not alter other skills, and is user-invocable. It relies on Membrane's hosted auth/session management rather than storing local secrets. Autonomous invocation remains enabled by platform default but is not combined with any additional privileges by this skill.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to manage PayKickstart and asks for no local secrets. Before installing/using it, consider: (1) You will need to install or run the @membranehq/cli (npm global install or npx) — review that package and be comfortable with a global npm install. (2) API requests and data will be proxied through Membrane's service (they handle auth and refresh); if your workflows include sensitive data, confirm you trust Membrane's provider and review their privacy/security docs. (3) The skill is instruction-only (no code bundled), so risk is limited to the CLI you install and the network interactions the skill performs.Like a lobster shell, security has layers — review code before you run it.
latestvk973kygjt3pxhydfs9rvxk5xc5843qpr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.