Funraise

v1.0.2

Funraise integration. Manage data, records, and automate workflows. Use when the user wants to interact with Funraise data.

0· 75·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The SKILL.md describes a Funraise integration implemented by calling the Membrane CLI and proxying to Funraise; the requested capabilities (network access, a Membrane account) match the stated purpose.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, creating a connection, listing actions, running actions, and proxying requests. They do not ask the agent to read unrelated files, environment variables, or post data to unknown endpoints.
Install Mechanism
This is an instruction-only skill that recommends installing @membranehq/cli via npm (-g) or using npx. That is a common approach but carries the usual npm-install risks (third-party code executed on install). No obscure download URLs or extract steps are used.
Credentials
The skill declares no required environment variables or credentials and explicitly advises using Membrane's connection flow rather than asking for API keys locally, which is proportionate to its function.
Persistence & Privilege
No elevated persistence is requested (always: false). The skill does not instruct modifying other skills or system-wide agent settings.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to interact with Funraise and does not request unrelated secrets. Before installing: (1) verify you trust the @membranehq/cli package (installing npm -g runs third-party code), (2) confirm the Membrane homepage/repository are the legitimate vendor you expect, and (3) avoid entering Funraise API keys locally — follow the described Membrane connection/browser auth flow. If you need stronger assurance, check the Membrane CLI package source on npm/GitHub and verify the connector IDs come from your Membrane tenant.

Like a lobster shell, security has layers — review code before you run it.

latestvk97052c5rs01sba7mg8c2k5rgd8436ye

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments