Agent skill · marketing growth · membranedev
vivocalendar
Vivocalendar integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vivocalendar data.
Why this skill is useful
Provides specific commands and workflows for integrating with Vivocalendar that the AI wouldn't reliably generate on its own.
What it needs
Requires @membranehq/cli installed locally. Requires membrane account access. About 4k tokens when loaded. Last updated 2026-04-28. 253 stars on the source repository.
What this skill does
Vivocalendar Vivocalendar is a calendar application, likely used for scheduling and organizing events. It's probably used by individuals or teams to manage their time and appointments. Official docs: https://developers.vivo.com/document/doc/en/resource/calendar Vivocalendar Overview Calendar Event Contact Working with Vivocalendar This skill uses the Membrane CLI to interact with Vivocalendar. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing. Install the CLI Install the Membrane CLI so you can run membrane from the terminal: Authentication This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available. Headless environments: The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with: Add --json to any command for machine-readable JSON output. Agent Types : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness Connecting to Vivocalendar Use membrane connection ensure to find or create a connection by app URL or domain: The user completes authentication in the browser. The output contains the new connection id. This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically. If the returned connection has state: "READY", skip to Step 2. 1b. Wait for the connection to be ready If the connection is in BUILDING state, poll until it's ready: The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING. The resulting state tells you what to do next: READY — connection is fully set up. Skip to Step 2. CLIENTACTIONREQUIRED — the user or agent needs to do something. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills membranedev/vivocalendar