Cirrus Labs
v1.0.0Cirrus Labs integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cirrus Labs data.
⭐ 0· 50·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
medium confidencePurpose & Capability
Name/description state a Cirrus Labs integration and the SKILL.md consistently instructs the agent to use Membrane to connect to Cirrus; requested actions (connector discovery, connection, action runs, proxy requests) match the stated purpose.
Instruction Scope
Instructions focus on installing and using the Membrane CLI, creating a connection, listing actions, running actions, and proxying API requests. The SKILL.md does not ask the agent to read unrelated files, system state, or secrets, and explicitly advises not to request API keys from the user.
Install Mechanism
This is an instruction-only skill (no install spec) but tells users to run `npm install -g @membranehq/cli`. Relying on a public npm package is reasonable for a CLI, but global npm installs can execute arbitrary install-time scripts; the registry metadata does not include an automated install spec or package integrity checks.
Credentials
The skill declares no required env vars or credentials and instructs using Membrane-managed connections (browser OAuth flow). The requested access (auth via Membrane) is proportional to the stated goal, though it does mean the Membrane service will see/hold the Cirrus credentials.
Persistence & Privilege
The skill is not set to always:true and has no install-time actions in the registry. It does not request permanent agent-wide privileges or modify other skills' configs.
Assessment
This skill delegates auth and API calls to the Membrane service and asks you to install the @membranehq/cli npm package. Before installing: 1) Verify you trust Membrane (they will broker access to your Cirrus account and store/refresh credentials). 2) Inspect the @membranehq/cli package/repo and consider installing in a controlled environment rather than globally. 3) Be aware that proxying requests through Membrane means Cirrus data and operations are routed via a third party—confirm this is acceptable for your data sensitivity and compliance requirements.Like a lobster shell, security has layers — review code before you run it.
latestvk97awy64ztgs8w5v1659mzghe184fwzy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.