Calendso
v1.0.2Calendso integration. Manage data, records, and automate workflows. Use when the user wants to interact with Calendso data.
⭐ 0· 101·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
Name/description (Calendso integration) match the instructions: all commands target the Membrane CLI to discover connectors/actions and to proxy Calendso API calls. No unrelated environment variables, binaries, or system paths are requested.
Instruction Scope
SKILL.md confines actions to installing/using the @membranehq/cli and running membrane commands (login, connect, action list/run, request). It does not instruct reading arbitrary local files or harvesting unrelated environment variables. Note: using the Membrane proxy means your Calendso requests and data will be routed through Membrane's service, so you must trust that provider with those requests and any data transmitted.
Install Mechanism
No install spec in the registry (skill is instruction-only). The docs instruct installing the Membrane CLI via npm (global) or using npx. Installing a global npm package is a common but system-modifying action; prefer npx or review the package source before global install.
Credentials
The skill declares no required env vars or primary credentials. Authentication is handled via Membrane's browser-based login flow (no local API keys requested), which is proportionate to the described workflow.
Persistence & Privilege
The skill does not request persistent/always-on privileges and has default autonomous-invocation settings. It does not ask to modify other skills or system-wide settings.
Assessment
This skill appears internally consistent, but before installing: (1) Confirm you trust Membrane (https://getmembrane.com) because the CLI and proxy will route Calendso API requests through their service and they will handle your credentials; (2) prefer using npx or inspect the @membranehq/cli package source on npm/GitHub rather than doing a global npm install; (3) avoid running the CLI on highly sensitive machines unless you understand what data will be proxied; (4) verify connector/connection IDs and permissions during setup; and (5) if you need assurance about data handling, review Membrane's docs and privacy/security policies before granting access.Like a lobster shell, security has layers — review code before you run it.
latestvk97e8vs4f5xw23dkqn8paygt3h84321r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.