Fireberry
v1.0.2Fireberry integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Fireberry data.
⭐ 0· 85·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 (Fireberry CRM integration) matches the instructions: all actions are performed via the Membrane CLI and the skill describes listing/creating/updating CRM objects. No unrelated services, binaries, or credentials are requested.
Instruction Scope
SKILL.md instructs the agent/user to install and use the Membrane CLI, run login flows, list/create connections, run pre-built actions, or proxy requests to the Fireberry API via Membrane. The instructions do not ask the agent to read arbitrary local files or to exfiltrate unrelated data.
Install Mechanism
There is no embedded install spec, but the documentation instructs the user to run `npm install -g @membranehq/cli`. Installing a global npm package is a reasonable requirement for this integration, but it is a privileged action on the host and should be verified (check the package on npm/github) before running.
Credentials
The skill declares only network access and a Membrane account as requirements. No environment variables, secrets, or unrelated credentials are requested in the skill metadata or instructions.
Persistence & Privilege
always is false and the skill does not request persistent system-wide configuration or access to other skills' credentials. Autonomous invocation is allowed by default (normal) but not combined with any other broad privileges.
Assessment
This skill is coherent for integrating Fireberry via Membrane, but before installing or running anything: 1) Verify @membranehq/cli on npm and the vendor (getmembrane.com / the referenced GitHub) to ensure the CLI is trustworthy; 2) if you don't want a global npm package on your machine, consider running the CLI in a container or dedicated VM; 3) understand that Membrane will handle and store credentials for Fireberry and will proxy API requests — treat Membrane as a trusted intermediary and review its privacy/security docs; 4) avoid sending highly sensitive data in ad-hoc proxy requests and review action input schemas before running actions. If you want a deeper assessment, provide the actual npm package/repository URL for @membranehq/cli so its code/release provenance can be reviewed.Like a lobster shell, security has layers — review code before you run it.
latestvk97cpwz22d6s002h3dhwq5mzx9842gnz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.