Cloudflare R2
v1.0.0Cloudflare R2 integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cloudflare R2 data.
⭐ 0· 12·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 runtime instructions: the SKILL.md documents using the Membrane CLI to manage Cloudflare R2 objects and connections. All required actions (connect, list actions, run actions, proxy requests) are consistent with an R2 integration.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, logging in, creating/listing connections, and proxying requests to Cloudflare R2. They do not instruct reading unrelated local files or environment variables. Note: the skill advises using Membrane's proxy for arbitrary R2 API calls, which means data and credentials will flow through Membrane's service — expected for this design but worth user attention.
Install Mechanism
This is an instruction-only skill (no automated installer). It tells users to run 'npm install -g @membranehq/cli' or use 'npx', which is reasonable for a CLI-based integration. Installing a global npm package modifies the system PATH and should be done intentionally; the skill itself does not perform installation.
Credentials
The skill declares no required env vars or credentials (Membrane handles auth). This is proportional for a proxy-based design, but has a trust implication: Membrane will hold and refresh the Cloudflare R2 credentials server-side and will see proxied requests and responses.
Persistence & Privilege
The skill does not request persistent or elevated platform privileges (always:false). It's user-invocable and does not modify other skills or system settings per the provided metadata.
Assessment
This skill is coherent but depends on trusting Membrane as a middleman. Before installing or using it: 1) Review Membrane's security, privacy, and credential storage practices (getmembrane.com and docs). 2) Prefer npx to avoid global npm installs if you don't want to modify system-wide PATH. 3) When creating Cloudflare R2 connections, grant least privilege (narrow scope keys) where possible. 4) Understand that proxied API calls and stored credentials will be visible to Membrane — if you need to keep data or keys entirely under your control, consider a different integration that uses your own client-side credentials. 5) Run CLI commands as a normal user (not root) and verify connector IDs and action inputs before executing operations that modify data.Like a lobster shell, security has layers — review code before you run it.
latestvk9725rq788mc5f0y1k6q25ntdx84dy12
License
MIT-0
Free to use, modify, and redistribute. No attribution required.