Caspio

v1.0.0

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

0· 51·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Caspio integration) match the instructions, which explain how to install and use the Membrane CLI to connect to Caspio, run actions, and proxy API requests. Nothing requested is unrelated to a third‑party API integration.
Instruction Scope
SKILL.md limits actions to installing and using the Membrane CLI, creating connections, listing/running actions, and proxying requests. It does not instruct reading unrelated files, harvesting environment variables, or sending data to unexpected endpoints beyond Membrane/Caspio.
Install Mechanism
Installation is an npm global package (npm install -g @membranehq/cli). This is an expected mechanism for a CLI integration but carries the usual risks of a globally installed npm package; it will execute code on the host once installed and should be installed from a trusted source.
Credentials
The skill declares no required env vars, no config paths, and relies on Membrane to handle credentials. It does not request unrelated secrets or broad environment access.
Persistence & Privilege
always is false and there are no install scripts or config modifications in the skill itself. The skill is instruction-only and does not request persistent elevated privileges.
Assessment
This skill is internally consistent: it tells you to install the Membrane CLI and to create a Caspio connection via Membrane rather than asking for API keys. Before installing, verify you trust the Membrane project and the npm package (@membranehq/cli) (check the package page, publisher, and GitHub repo). Installing a global npm CLI executes code on your machine — prefer installing in a controlled environment or reviewing the package source first. Remember Membrane will proxy requests (so Caspio traffic goes through Membrane servers); review their privacy/security docs and your organisation's policy for routing data through third parties. If you need stronger assurance, ask for the package checksum/release artifacts or run the CLI in an isolated environment. Finally, consider whether you want to allow the agent to invoke this skill autonomously (default behavior) when it can interact with your Caspio data.

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

latestvk97adf840dqeb6g0ae51xbfqmh84e6fs

License

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

Comments