Focalboard
v1.0.2Focalboard integration. Manage data, records, and automate workflows. Use when the user wants to interact with Focalboard data.
⭐ 0· 74·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
Name and description match the runtime instructions: the skill instructs the agent to use the Membrane CLI to interact with Focalboard. No unrelated services, env vars, or binaries are requested.
Instruction Scope
SKILL.md stays in-scope: it tells the user/agent to install and use the Membrane CLI, run login flows, list/connect actions, proxy requests, and run actions. There are no instructions to read unrelated local files or exfiltrate data.
Install Mechanism
The doc instructs installing @membranehq/cli via npm (-g). This is expected for a CLI integration but carries the usual moderate risk of running third-party npm packages globally; the skill itself has no install spec and is instruction-only.
Credentials
No environment variables or local config paths are required. The skill explicitly directs credentials to be managed by Membrane and not to ask users for API keys, which is proportionate to the stated design.
Persistence & Privilege
No elevated privileges or permanent presence requested. always is false and the skill does not request modifying other skills or system-wide configs.
Assessment
This skill is coherent and uses Membrane as the proxy to Focalboard. Before installing or following its instructions: 1) Verify the @membranehq/cli package on the npm registry and that the publisher matches the project/homepage (getmembrane.com). 2) Be aware that installing global npm CLIs runs third-party code—avoid installing as root and review the package if you have concerns. 3) Trusting this skill implies trusting the Membrane service to handle authentication and data proxying; if you require self-hosted or on-prem control, confirm Membrane's deployment model and privacy policy first. 4) For automated or headless environments, follow the documented headless login flow and avoid pasting secrets into open channels.Like a lobster shell, security has layers — review code before you run it.
latestvk97ejd6stsnc4a6bbqhga2dxcn843n67
License
MIT-0
Free to use, modify, and redistribute. No attribution required.