ClawHub

Four Js Development Tools

v1.0.2

Four J's Development Tools integration. Manage data, records, and automate workflows. Use when the user wants to interact with Four J's Development Tools data.

⭐ 0· 94·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
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (Four J's Development Tools integration) matches the runtime instructions (use Membrane CLI to connect, list actions, run actions and proxy API requests). The declared homepage and repository references align with the described integration.
✓
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, logging in via browser, creating/listing connections, running actions, and proxying requests. It does not instruct reading unrelated files, exporting secrets, or contacting unexpected endpoints beyond Membrane/Four J's APIs.
ℹ
Install Mechanism
This is an instruction-only skill (no install spec in metadata), but it directs the user to run a global npm install (-g @membranehq/cli). Installing a global npm package changes the host environment and relies on the npm registry/package integrity — expected for a CLI but worth reviewing before installing (consider using npx to avoid global install).
✓
Credentials
The skill declares no required env vars or credentials. It explicitly relies on Membrane-managed connections and browser-based user authentication, which is proportionate to the described functionality.
✓
Persistence & Privilege
Skill is not always-enabled and is user-invocable. The only persistent state implied is the Membrane CLI login/session (normal for CLI tools). There is no request to modify other skills or system-wide configs.
Assessment
This skill appears coherent, but before installing: (1) verify the npm package name (@membranehq/cli) and inspect the package/repo to ensure authenticity; (2) prefer using npx for one-off actions to avoid global installation if you want limited system changes; (3) be aware Membrane acts as a proxy — request/response payloads and auth tokens are handled server-side by Membrane, so only proceed if you trust their service and privacy policy; (4) perform the browser-based login yourself (do not paste secrets into chat) and verify connector IDs before granting access.

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

latestvk97cy52pzd6n3g67g6sfp5xw8h8425zz

License

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

Comments