Kickfire
v1.0.2KickFire integration. Manage data, records, and automate workflows. Use when the user wants to interact with KickFire data.
⭐ 0· 96·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
medium confidencePurpose & Capability
The skill describes KickFire integration and the SKILL.md consistently instructs using the Membrane CLI to connect, list actions, run actions, or proxy requests to KickFire. Requiring the Membrane CLI (and a Membrane account) is coherent with the stated purpose; there are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI (login, create connection, list/run actions, proxy requests). They do not instruct reading unrelated files or asking for local secrets. However, the runtime flow sends requests and credentials through Membrane's servers (proxy + auth handling), which is a privacy/trust consideration the user should understand.
Install Mechanism
This is an instruction-only skill (no install spec), but it tells users to install a global npm package (@membranehq/cli). Installing a global npm CLI is common but does execute third-party code on the host — users should review the package source/repo before installing.
Credentials
The skill itself does not request environment variables or credentials, which is appropriate. Still, the design delegates credential management and proxied API calls to Membrane, meaning Membrane will receive and store KickFire auth tokens and proxied request data — this is expected for the integration but requires trusting Membrane.
Persistence & Privilege
The skill does not request always: true, does not modify other skills, and does not require persistent system-level privileges. It is user-invocable and allows normal autonomous invocation (platform default).
Assessment
This skill appears to do what it claims: it teaches the agent to use the Membrane CLI to connect to KickFire and run actions. Before installing or using it, verify the @membranehq/cli package and GitHub repository, review Membrane's privacy/security documentation (you will be routing KickFire auth and proxied requests through their service), and consider testing with non‑production credentials or an isolated account. If you prefer not to run a third‑party CLI globally, inspect the package source or use npx for one-off runs.Like a lobster shell, security has layers — review code before you run it.
latestvk978achk80a6ak79geysq6dqcd843qw2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.