Railway
v1.0.2Railway integration. Manage data, records, and automate workflows. Use when the user wants to interact with Railway data.
⭐ 0· 83·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 and description claim a Railway integration and the instructions consistently show how to use the Membrane CLI to connect to Railway, discover actions, run them, and proxy Railway API calls. Required inputs (a Membrane account and network access) match the described purpose.
Instruction Scope
SKILL.md stays on-task: it instructs installing the Membrane CLI, performing browser-based login, creating connections, listing actions, running actions, and using Membrane's proxy. It does not instruct reading unrelated files, grabbing unrelated env vars, or exfiltrating data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec). The doc recommends `npm install -g @membranehq/cli` (or using npx). Installing a global npm CLI will fetch code from the public npm registry — this is expected for a CLI but carries the usual risk of executing third-party code. Using npx avoids a global install.
Credentials
No environment variables or credentials are declared or requested by the skill. The only external requirement is a Membrane account (handled via browser login) which is proportional to the task. The SKILL.md explicitly advises not to ask the user for API keys, and to let Membrane manage auth.
Persistence & Privilege
always is false, no install spec writes persistent files as part of the skill itself, and the skill does not request elevated platform privileges or modify other skills' configs. Normal autonomous invocation remains possible (platform default).
Assessment
This skill appears coherent: it uses the Membrane CLI to talk to Railway and asks only for a Membrane account and network access. Before installing or running commands: (1) verify the npm package (@membranehq/cli) and the Membrane project (homepage/repo) are the official sources you trust; (2) prefer `npx @membranehq/cli` if you want to avoid a global install; (3) when you run `membrane connect` review the permissions requested for the Railway connection; and (4) don't paste secrets into chat — authentication is done through the browser login flow. If you need higher assurance, inspect the CLI repository code or run the CLI in a restricted environment (container/VM).Like a lobster shell, security has layers — review code before you run it.
latestvk97csgh1269gj9zjhhwanhjmch8426qs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.