Florm

v1.0.2

Florm integration. Manage Organizations. Use when the user wants to interact with Florm data.

0· 90·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Florm integration) matches the instructions (use Membrane CLI to connect to Florm, list actions, run actions, and proxy requests). Required network access and a Membrane account are appropriate and expected.
Instruction Scope
SKILL.md is explicit: it instructs installing and using the @membranehq CLI, performing browser-based login, creating connections, listing actions, running actions, and proxying requests to Florm via Membrane. It does not ask the agent to read unrelated system files, environment variables, or transmit data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec), but it tells users to install a global npm package (npm install -g @membranehq/cli). Installing a third-party CLI is a normal step for this integration but carries the usual trust considerations for npm packages.
Credentials
No environment variables, credentials, or config paths are requested by the skill. The SKILL.md explicitly recommends letting Membrane manage credentials rather than asking users for keys, which is proportionate.
Persistence & Privilege
The skill is not always-on and does not request elevated persistence or modify other skills or system-wide agent settings. Autonomous invocation remains allowed by platform default but there are no additional privileges requested.
Assessment
This skill is coherent: it instructs use of the Membrane CLI to connect to Florm and does not request secrets or unrelated system access. Before installing, verify you trust the @membranehq npm package and the Membrane service (review publisher and package provenance), perform the npm install in an account/environment you control (avoid running installs as root), and grant only the minimum Florm/organization permissions when creating connections. If you're concerned about running third‑party CLIs, consider reviewing the CLI source code or using an isolated/test environment. Note: the skill relies on network access and your Membrane account/browser-based auth to function.

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

latestvk975fabm7y4y6fj5wcbams1zb5843ekm

License

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

Comments