Firehydrant

v1.0.2

FireHydrant integration. Manage data, records, and automate workflows. Use when the user wants to interact with FireHydrant data.

0· 72·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (FireHydrant integration) align with the instructions: all actions use the Membrane CLI to discover connectors, create connections, run actions, or proxy requests to the FireHydrant API. Nothing in the SKILL.md asks for unrelated privileges or services.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, authenticating via Membrane, listing/connecting actions, running actions, and proxying API requests through Membrane. The doc explicitly tells agents not to ask users for API keys and does not direct reading unrelated files, env vars, or system paths.
Install Mechanism
No install spec in the skill bundle itself (instruction-only). The SKILL.md instructs installing @membranehq/cli via npm (a standard public registry). This is a normal mechanism but installing a global npm CLI changes local system state and pulls code from npm — users should trust the @membranehq package before installing.
Credentials
The skill declares no required env vars, no primary credential, and no config paths. It requires a Membrane account and network access, which are proportionate to a proxy-based integration that delegates auth to Membrane.
Persistence & Privilege
Skill does not request always:true, does not modify other skills or system-wide agent settings, and is user-invocable. No persistent privileged presence or hidden autorun behavior is requested.
Assessment
This skill delegates all auth and API calls to the Membrane service and instructs you to install the @membranehq CLI. Before installing or using it, verify you trust Membrane (review its npm package, privacy, and security docs) because proxying requests through Membrane means that service will see FireHydrant API traffic and handle credentials. Installing the CLI globally (npm install -g) modifies your system's PATH — if you prefer, use npx to run commands without a global install. Otherwise, no inconsistencies or unexplained credential requests were found.

Like a lobster shell, security has layers — review code before you run it.

latestvk97eqhjjgf9sy0zkctwwxmgs2h842mvz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments