Propeller

v1.0.0

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

0· 58·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 match the runtime instructions: the skill tells the agent to use the Membrane CLI to manage Propeller data. Requiring the Membrane CLI and a Membrane account is proportionate to the stated goal.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, logging in via browser (or headless complete flow), listing/connecting actions, running actions, and proxying requests through Membrane. It does not ask the agent to read unrelated system files, exfiltrate secrets, or call unexpected endpoints.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the SKILL.md tells users to run `npm install -g @membranehq/cli` or use `npx`. Pulling a CLI from the public npm registry is expected for this use case but carries the usual moderate risk of installing third-party code; the referenced homepage and repository appear to match the vendor.
Credentials
The skill requests no environment variables or local secrets. It explicitly instructs to rely on Membrane-managed connections (browser auth) rather than asking the user for API keys. The only sensitive trust is placing Propeller credentials in Membrane's connection flow — appropriate but requires trusting Membrane.
Persistence & Privilege
Flags are default (always: false, user-invocable: true, model invocation allowed). The skill does not request persistent system-wide changes or access to other skills' configs.
Assessment
This skill is internally consistent: it uses the Membrane CLI to perform Propeller actions and does not request unrelated credentials. Before installing, verify you trust Membrane/@membranehq (they will handle and store your Propeller connection), and prefer running the CLI via npx or review the npm package (https://www.npmjs.com/package/@membranehq/cli) before a global install. Be aware global npm installs may require elevated privileges and install executables on your PATH. If you do not want to rely on a third party to hold your Propeller credentials, do not create a Membrane connection.

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

latestvk972930e5wd38rfwbs5518tnp5849d87

License

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

Comments