Donately
v1.0.2Donately integration. Manage Organizations, Projects, Users. Use when the user wants to interact with Donately data.
⭐ 0· 137·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 describes using Membrane to manage Donately entities. All requested capabilities (connect, run actions, proxy requests) are directly relevant to a Donately integration.
Instruction Scope
The SKILL.md tells the agent/operator how to install and use the Membrane CLI, run connector discovery, create connections, call pre-built actions, and proxy raw requests to the Donately API. It does not instruct reading unrelated files or exporting secrets. Note: it does instruct a global npm install and opening a browser for auth (or using a headless flow), which are expected for this workflow.
Install Mechanism
This is an instruction-only skill (no install spec). It recommends installing @membranehq/cli via npm -g. Installing a public npm package is a standard choice for a CLI, but global npm installs require elevated file-system access and the package's trustworthiness should be verified (check npmjs and the project's GitHub). No opaque downloads or extract steps are present.
Credentials
The skill declares no required env vars, no credentials, and explicitly tells users not to supply API keys (Membrane handles auth). The environment/credential access requested is minimal and appropriate for the stated purpose.
Persistence & Privilege
always is false and the skill does not request system-wide config changes or persistent privileges. It relies on the Membrane CLI and the user's browser-based login flow; autonomous invocation is allowed (platform default) but is not accompanied by unusual privileges.
Assessment
This skill is coherent: it uses the Membrane CLI to connect to Donately and does not ask for unrelated secrets. Before installing, verify the @membranehq/cli package and project (npm/GitHub) so you trust the CLI you will run globally. Be aware the workflow opens a browser for OAuth-style login (or a headless code flow); only complete that flow on the official Membrane pages. Installing a global npm CLI requires filesystem privileges—use your usual caution for global installs. If you prefer not to install a global package, evaluate running the CLI in a contained environment (container or virtual environment) or confirm an approved system package is available.Like a lobster shell, security has layers — review code before you run it.
latestvk97fbs84gqwq1y2ds30js0vjgh843e7a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.