Redcircle Api
v1.0.2RedCircle API integration. Manage Organizations, Users, Activities, Notes, Files. Use when the user wants to interact with RedCircle API 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 skill name/description match the runtime instructions: it tells the agent to use the Membrane CLI to connect to RedCircle and run proxyed actions. There are no unrelated credentials, binaries, or functionality requested.
Instruction Scope
SKILL.md instructs only Membrane CLI flows (install CLI, login, create connection, list actions, run actions, or proxy requests). It does not instruct reading unrelated files, environment variables, or sending data to unexpected endpoints. The one implicit scope decision is that API credentials and requests are routed through Membrane's service (declared in the docs).
Install Mechanism
There is no manifest install spec, but the README tells users to install @membranehq/cli via npm (-g). This is an expected approach for a CLI-driven integration; installing a public npm package has moderate trust implications (you should confirm package provenance and review privileges for global installs).
Credentials
The skill declares no required env vars or secrets and relies on Membrane's browser-based login/connector flow. This is proportionate to the stated purpose, but it does require trusting Membrane to hold/refresh RedCircle credentials and proxy requests on your behalf.
Persistence & Privilege
The skill is instruction-only, not always-enabled, and requests no system-wide config changes or additional privileges. It does not modify other skills or agent settings.
Assessment
This skill appears coherent: it teaches use of the Membrane CLI to connect to RedCircle and does not request unrelated secrets. Before installing/using it: 1) verify the @membranehq/cli package on npm (author, download counts, repo) to ensure it's authentic; 2) review Membrane's privacy/security docs because your RedCircle credentials and proxied requests will be handled by Membrane's service; 3) avoid running global installs on systems you don't control (use a container/VM or nvm-managed node); and 4) when creating connections, confirm connector IDs and action outputs before executing destructive actions (DELETE/POST) through the proxy.Like a lobster shell, security has layers — review code before you run it.
latestvk9764csk71m4xcfvatgadk69sx843prt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.