Coder
v1.0.0Coder integration. Manage data, records, and automate workflows. Use when the user wants to interact with Coder data.
⭐ 0· 54·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
The skill's name/description (Coder integration) matches the instructions: discover/connect to a Coder connector, list and run actions, and proxy requests. No unrelated services, binaries, or credentials are requested.
Instruction Scope
All runtime instructions are limited to installing/using the Membrane CLI, authenticating via membrane login, discovering connections/actions, running actions, and proxying requests. Important privacy note: proxying sends requests through Membrane's service (it will see request URLs, bodies, and responses), which is expected for this architecture but relevant for sensitive data.
Install Mechanism
This is an instruction-only skill (no install spec). It tells the user to install the official @membranehq/cli via npm -g, which is a standard, expected step for using the CLI; the skill itself does not auto-download or execute code.
Credentials
No environment variables, primary credential, or config paths are requested. Authentication is handled interactively via the Membrane login flow, which is proportionate to the stated purpose.
Persistence & Privilege
The skill is not always-included and does not request elevated persistence or modification of other skills or system-wide configs. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.
Assessment
This skill appears internally consistent: it requires the Membrane CLI and a Membrane account to act as a proxy to Coder. Before installing/using it, confirm you trust Membrane (getmembrane.com/@membranehq and @membranehq/cli on npm) because API requests and payloads will transit their service. Installing the CLI requires npm -g (may need admin privileges); in automated or high-security environments prefer manual review of the CLI and Membrane's privacy/auth docs. If you cannot trust Membrane with request data, do not use this integration.Like a lobster shell, security has layers — review code before you run it.
latestvk9753bjcpvr23tppb8tsy37pnd84eb7r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.