Planyo Online Booking
v1.0.2Planyo Online Booking integration. Manage data, records, and automate workflows. Use when the user wants to interact with Planyo Online Booking data.
⭐ 0· 78·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
The name/description (Planyo integration) match the instructions: everything is centered on using the Membrane CLI to connect to Planyo and run actions or proxied API requests. There are no unrelated credential or binary requirements.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, logging in via browser, creating/using connections, listing and running actions, and proxying requests to Planyo. It does not ask the agent to read arbitrary files, access unrelated environment variables, or exfiltrate data to unknown endpoints.
Install Mechanism
This is an instruction-only skill (no install spec) but it tells users to install the public npm package @membranehq/cli globally. That is expected for a CLI-based integration, but installing global npm packages carries the usual trust considerations (verify package origin/repo).
Credentials
The skill declares no required environment variables or credentials and explicitly instructs not to ask users for API keys, relying on Membrane to manage auth. The requested scope is minimal and proportional to a connector-based integration.
Persistence & Privilege
Flags are default (always: false, user-invocable true, agent invocation allowed). The skill does not request permanent presence or system-wide configuration changes.
Assessment
This skill delegates all auth and API calls to the Membrane service via the @membranehq/cli. Before installing or using it: 1) Verify the Membrane CLI package and repository (https://github.com/membranedev/application-skills and https://getmembrane.com) are trustworthy; 2) Be cautious installing global npm packages—prefer reviewing the package source first; 3) When authenticating, review the OAuth scopes/permissions presented by Membrane and Planyo in the browser; 4) Do not enter Planyo API keys into the skill—follow the connection flow so Membrane stores credentials server-side as intended. No code files were provided, so the static scanner had nothing to analyze; inspect Membrane docs or repo if you need stronger assurance.Like a lobster shell, security has layers — review code before you run it.
latestvk97c5cjhpc5n61h8tdzgphfdrx843mv4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.