Rutter
v1.0.2Rutter integration. Manage data, records, and automate workflows. Use when the user wants to interact with Rutter 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
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (Rutter integration) align with the instructions: all runtime steps use Membrane to connect to Rutter and run actions. Required tools and secrets declared in the SKILL.md (a Membrane account and network) match the stated purpose.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Rutter. They do not instruct reading unrelated files or environment variables. Note: the instructions will cause authentication flows and proxying of API requests through Membrane (expected for this integration).
Install Mechanism
This is an instruction-only skill (no code), so nothing is installed automatically. The SKILL.md tells the user to run `npm install -g @membranehq/cli` (and uses npx in examples). That is a reasonable, traceable npm package install, but installing global npm packages carries the usual supply-chain and privilege considerations; verify the package and its publisher before installing.
Credentials
The skill declares no required env vars, no credentials, and no config paths. It explicitly delegates auth to Membrane (telling the user not to provide API keys). This is proportionate to the described purpose.
Persistence & Privilege
always is false and the skill does not require persistent system changes. It relies on the user to run CLI commands and log in to Membrane; it does not request elevated or cross-skill privileges.
Assessment
This skill delegates all auth and proxying to the Membrane service and asks you to install the @membranehq/cli npm package. Before proceeding, (1) confirm you trust Membrane (review the package on npm/GitHub and the company privacy/security docs), (2) be aware your Rutter data and credentials will be mediated by Membrane (read their data handling and retention policies), (3) prefer running the CLI in a controlled environment (not on sensitive production hosts) if you have concerns about installing global npm packages, and (4) test with least-privilege accounts or sandbox data first.Like a lobster shell, security has layers — review code before you run it.
latestvk97dkpecxanfdpgb024f9n420s842fjk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.