Cyclr
v1.0.0Cyclr integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cyclr data.
⭐ 0· 53·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/description match the instructions: the SKILL.md explains how to use the Membrane CLI to manage Cyclr connectors, connections, flows, webhooks, secrets, etc. Nothing in the instructions requests access to unrelated services or credentials.
Instruction Scope
Runtime instructions are limited to installing and using the @membranehq/cli, logging in (browser-based or headless flow), and invoking membrane CLI commands to operate Cyclr resources. The instructions do not direct the agent to read arbitrary local files, unrelated environment variables, or exfiltrate data to unexpected endpoints beyond the integration platform and configured webhooks.
Install Mechanism
There is no packaged install spec in the registry; the SKILL.md instructs users to run 'npm install -g @membranehq/cli'. Using a public npm package is expected for a CLI, but global npm installs run third-party code on the host and carry the usual supply-chain risk. The repo/homepage links point at reasonable domains (GitHub, getmembrane.com).
Credentials
The skill declares no required environment variables or credentials. Authentication is handled by the Membrane CLI (browser-based or headless flow), which is appropriate for this purpose. The SKILL.md does reference API keys/secrets as Cyclr resources (expected) but does not ask for unrelated host credentials.
Persistence & Privilege
always is false and no install spec writes files via the registry. The skill relies on a user-installed CLI which will store its own auth tokens locally; that is expected behavior and does not modify other skills or system-wide agent settings.
Assessment
This skill appears to do what it says: it teaches the agent to use the Membrane CLI to manage Cyclr. Before installing or following the instructions, consider: 1) The SKILL.md recommends 'npm install -g @membranehq/cli' — installing any global npm package executes third-party code on your machine, so verify the package and maintainer (review the npm page and the GitHub repo). 2) The CLI performs browser-based authentication and will store tokens locally—if you use a shared system, be mindful of where those tokens are stored and who can access them. 3) The skill can create and run flows and webhooks inside Cyclr/Membrane; flows may call external endpoints you configure, so review any flows or connectors it creates before running them. 4) If you prefer lower risk, run the CLI in a sandboxed or dedicated environment (container or VM) and inspect the Membrane CLI source or package before global installation.Like a lobster shell, security has layers — review code before you run it.
latestvk97fx26xdqyq2vn4manxs1sy0s84dgnr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.