ClawHub

Flowtrack

v1.0.2

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

⭐ 0· 93·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 say 'FlowTrack integration' and the SKILL.md exclusively describes using the Membrane CLI to connect to FlowTrack, list actions, run actions, and proxy API requests — this is coherent and expected.
✓
Instruction Scope
Runtime instructions only cover installing/running the Membrane CLI, performing browser-based login, creating connections, listing/running actions, and proxying requests. The instructions do not request unrelated files, extra env vars, or exfiltrate data to unexpected endpoints.
✓
Install Mechanism
The skill recommends installing @membranehq/cli via npm (npx usage is also shown). Using npm for a CLI is expected for this purpose; no arbitrary downloads or archive extraction are suggested.
✓
Credentials
The skill declares no required environment variables or credentials. It relies on Membrane's browser-based connection flow for auth, which matches the stated guidance to avoid asking users for API keys.
✓
Persistence & Privilege
The skill is instruction-only, has no install spec or code files, and is not forced always-on. It does not request elevated platform privileges or to modify other skills' configurations.
Assessment
This skill is internally consistent: it uses the Membrane CLI to connect to FlowTrack and does not request environment secrets. Before installing, verify you trust @membranehq/@membranehq/cli (check the npm package, GitHub repo, and the getmembrane.com site), and prefer installing the CLI yourself rather than letting an automated agent run installation. Be aware that using the CLI and completing browser-based auth will grant Membrane-managed credentials access to FlowTrack on your behalf — review the connector permissions and revoke them in Membrane if needed. If you plan to run in headless or automated environments, double-check how the login flow and tokens are stored so you understand what the CLI will persist locally.

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

latestvk976na31175nyrgq7qf3w7swyd842fsc

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments