Reamaze
v1.0.2Reamaze integration. Manage data, records, and automate workflows. Use when the user wants to interact with Reamaze data.
⭐ 0· 85·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
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Reamaze integration) align with the instructions: all guidance is about using the Membrane CLI to connect to Reamaze and run actions or proxied API requests.
Instruction Scope
SKILL.md focuses on installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests. It does not instruct reading unrelated files, requesting local secrets, or sending data to unknown endpoints beyond Membrane/Reamaze.
Install Mechanism
No install spec in the registry; SKILL.md asks the user to run `npm install -g @membranehq/cli`. Installing a global npm package is a standard approach but carries the usual caution (global binary added/updated, network fetch from npm). This is moderate risk but expected for a CLI-based integration.
Credentials
The skill declares no required environment variables or secrets and explicitly says Membrane handles credentials and refresh. That matches the instructions which rely on browser-based OAuth via the Membrane CLI rather than asking for API keys.
Persistence & Privilege
Skill is instruction-only, does not request persistent system-wide config changes, and is not always-enabled. The default ability for the agent to invoke the skill autonomously is normal and not by itself a concern here.
Assessment
This skill is coherent: it tells the agent to use the Membrane CLI to access Reamaze and does not ask for local secrets. Before installing, verify you trust the Membrane project/package and the npm package name (@membranehq/cli), and review the OAuth scopes requested when you create the Reamaze connection (the Membrane flow will open a browser for auth). Installing a global npm CLI will add/replace a system binary — avoid doing that on a shared or sensitive host without review. If you need stricter control, ask the maintainer for a signed release, inspect the @membranehq/cli package source, or run the CLI in an isolated environment (container/VM).Like a lobster shell, security has layers — review code before you run it.
latestvk9702kcpwj3t2ep7ryhprha9qh8432n6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.