Flare
v1.0.0Flare integration. Manage data, records, and automate workflows. Use when the user wants to interact with Flare data.
⭐ 0· 101·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 skill declares itself as a Flare integration and all runtime instructions center on using the Membrane CLI to connect to Flare, list actions, run actions, and proxy API requests — this matches the description. Minor inconsistency: the top-level manifest lists no required binaries, yet the SKILL.md instructs users to install the Membrane CLI (npm). This is reasonable but worth noting.
Instruction Scope
SKILL.md stays within scope: it instructs how to install and use the Membrane CLI, create a connection, discover and run actions, and proxy requests to Flare. It does not direct reading of unrelated files, collection of unrelated credentials, or transmission to endpoints outside Membrane/Flare.
Install Mechanism
There is no automated install spec in the skill (instruction-only). It tells users to install @membranehq/cli via npm (or use npx). Installing an npm CLI is a common, expected step here, but it does carry normal third-party package risk — verify package provenance and prefer npx if you want to avoid a global install.
Credentials
No environment variables, secrets, or config paths are requested by the skill. The only external requirement is a Membrane account (server-side) and network access; Membrane will hold the Flare credentials for proxying, which is consistent with the stated design.
Persistence & Privilege
The skill does not request persistent inclusion (always:false). It does not ask to modify other skills or system-wide settings. Autonomous invocation is allowed by default (disable-model-invocation:false) but that is the platform normal; nothing else indicates elevated privileges.
Assessment
This skill is coherent and appears to do what it says: use the Membrane CLI to manage Flare. Before installing or using it, verify the @membranehq/cli package and the Membrane service are the official projects you expect (check the npm package page and upstream GitHub), review Membrane's privacy/permissions (Membrane will proxy and therefore have access to your Flare data), and consider using npx to avoid a global install. Because the skill relies on an external service for auth and proxying, ensure you trust that service before granting access.Like a lobster shell, security has layers — review code before you run it.
latestvk976fcpj7mjyq7ggxndgts58mn84gv54
License
MIT-0
Free to use, modify, and redistribute. No attribution required.