Vivocalendar
v1.0.0Vivocalendar integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vivocalendar data.
⭐ 0· 52·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's name and description (Vivocalendar integration) match the instructions: it uses the Membrane CLI to discover connectors, create connections, run actions, and proxy API requests to Vivocalendar. Required capabilities (network and a Membrane account) are appropriate for the stated purpose; no unrelated services or credentials are requested.
Instruction Scope
SKILL.md only instructs the agent to install and use the Membrane CLI, perform login flows, list connections/actions, run actions, and proxy requests. There are no instructions to read local unrelated files, access unspecified environment variables, or send data to unexpected endpoints. The guidance explicitly says not to ask users for API keys and to let Membrane handle auth.
Install Mechanism
The skill is instruction-only (no install spec), but it tells users/agents to install a global npm package (@membranehq/cli) or use npx. Installing an npm CLI is a legitimate choice for this integration, but global npm installs execute third-party code on the host — users should verify the package and publisher before installing. There is no automatic download/install in the skill manifest itself.
Credentials
The skill declares no required environment variables or credentials. All authentication is delegated to Membrane's login/connect flows. There are no disproportionate or unrelated credential requests in the manifest or the instructions.
Persistence & Privilege
Skill flags are default: not always-included and user-invocable. Autonomous invocation (disable-model-invocation=false) is the platform default; this skill does not request elevated persistence or attempt to modify other skills or system-wide settings.
Assessment
This skill is coherent: it only provides CLI instructions to connect to Vivocalendar through Membrane. Before proceeding, verify you trust getmembrane.com and the @membranehq/cli npm package (check the package author, repository, and recent releases) because installing global npm CLIs runs third‑party code on your machine. Be aware this skill relies on a Membrane account and browser-based OAuth flows — Membrane will hold connection credentials server-side. If you need to restrict autonomous behavior, consider disabling automatic skill invocation in your agent settings or test the workflow in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk97dx9xc4dpqcb7sjcdr21y1cx84ce0y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
