Firecom
v1.0.0Fire.com integration. Manage data, records, and automate workflows. Use when the user wants to interact with Fire.com data.
⭐ 0· 52·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
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (Fire.com integration) match the instructions and required actions: discover/connect to Fire.com via the Membrane platform. No unrelated environment variables, binaries, or config paths are requested.
Instruction Scope
SKILL.md confines runtime actions to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Fire.com. It does not instruct reading local files or unrelated credentials, nor does it direct data to unexpected endpoints outside Membrane/Fire.com.
Install Mechanism
The skill is instruction-only (no packaged install), but tells users to globally install @membranehq/cli via npm (and suggests npx usage). Installing a third-party CLI is expected for this integration but carries the usual risks of running externally maintained software from npm; this is proportionate to the stated purpose.
Credentials
No environment variables or local credentials are requested. The instructions explicitly delegate authentication to Membrane (server-side), which is coherent for this connector. Users should however understand that Membrane will hold/access their Fire.com credentials.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent platform privileges. Autonomous invocation is allowed (platform default) but there are no additional red flags combining with broad credential access or system-level changes.
Assessment
This skill appears coherent: it relies on the Membrane CLI to manage Fire.com connections and does not ask for unrelated secrets. Before installing, verify you trust getmembrane.com/@membranehq and the npm package @membranehq/cli (review its npm page and source repo), prefer using npx for one-off runs instead of a global install if you want less persistent change, and be aware that authenticating will give Membrane access to your Fire.com account (server-side). If you need tighter control, confirm what actions the connection is permitted to perform in your Membrane/Fire.com settings before granting access.Like a lobster shell, security has layers — review code before you run it.
latestvk97b9zdezgcp4qjp4c90pzdhrd84eenp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.