Workboard
v1.0.2Workboard integration. Manage Organizations. Use when the user wants to interact with Workboard data.
⭐ 0· 114·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
OpenClaw
Benign
high confidencePurpose & Capability
The skill claims to integrate with Workboard and all runtime instructions show use of the Membrane CLI to discover connectors, create connections, run pre-built actions, or proxy API requests to Workboard — which is coherent with the stated purpose.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, logging in, creating/using a Workboard connection, listing actions, running actions, and proxying requests. Note: the documented proxy feature allows sending arbitrary Workboard API requests via Membrane once a connection is authorized — this is expected for an integration but gives broad API access to whatever account is connected, so users should be cautious when authorizing connectors or running custom proxy requests.
Install Mechanism
Install is via a public npm package (@membranehq/cli) invoked with npm install -g; this is a common distribution method and no unknown download URLs or archive extraction are used. Installing global CLIs has normal operational risk but is proportional to the task.
Credentials
The skill declares no required environment variables or secrets. It requires a Membrane account and network access, which are appropriate for a third-party integration that centralizes credentials.
Persistence & Privilege
The skill is instruction-only, does not request always: true, and does not alter other skills or system-wide settings. Autonomous invocation remains enabled (platform default) but there is no additional persistence or privilege requested by the skill itself.
Assessment
This skill appears internally consistent: it uses the Membrane CLI to handle auth and interact with Workboard, and does not ask for unrelated credentials. Before installing, confirm you trust the @membranehq/cli npm package and the Membrane service (they will broker access to your Workboard account). Be cautious when authorizing a connector (it grants the CLI/service broad API access to the connected Workboard account) and avoid pasting secrets into chat. If you need stricter controls, consider creating a limited-scope Workboard account or reviewing Membrane's connector permissions before connecting.Like a lobster shell, security has layers — review code before you run it.
latestvk977dj3n174qj3z1124b32sgps8426db
License
MIT-0
Free to use, modify, and redistribute. No attribution required.