render-cli

Automates Render service deploys, logs, SSH, and psql operations from the terminal.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/greenmartialarts/EventCore --skill render-cli-greenmartialarts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-cli
Source: https://github.com/greenmartialarts/EventCore/tree/main/.junie/skills/render-cli
Command: npx skills add https://github.com/greenmartialarts/EventCore --skill render-cli-greenmartialarts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing Render services through the Dashboard is slow for repetitive operations and impossible to script in CI/CD pipelines. This Skill provides the commands and patterns to install, authenticate, and operate the Render CLI for deploys, logs, database access, and Blueprint validation from any terminal or automation environment. ## Core Features & Use Cases - Deployment Automation: Trigger deploys with render deploys create, wait for completion, and deploy specific commits or Docker images with non-interactive flags. - Operational Access: Tail logs in real time, SSH into running instances or ephemeral shells, and run psql queries against Render Postgres with JSON or CSV output. - CI/CD Integration: Authenticate with RENDER_API_KEY, force machine-readable output with -o json and --confirm, and script the full workflow in GitHub Actions. - Use Case: A team wants every merge to main to deploy automatically. Install the CLI in a GitHub Actions job, set RENDER_API_KEY as a secret, and run render deploys create <service-id> --wait --confirm -o json so the pipeline fails if the deploy fails. ## Quick Start Install the Render CLI, authenticate with an API key, and trigger a deploy for my service while waiting for it to complete.

Frequently Asked Questions about render-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Render service from the command line?

Run `render deploys create <service-id> --wait --confirm -o json` to trigger a deploy and wait for completion. The command exits non-zero on failure, making it suitable for CI pipelines. You can also pin a specific commit with `--commit` or a Docker image with `--image`.

How do I authenticate the Render CLI in CI/CD pipelines?

Set the `RENDER_API_KEY` environment variable with an API key generated from Account Settings > API Keys in the Render Dashboard. API keys do not expire and take precedence over CLI tokens, so no `render login` step is needed in automation.

How do I query a Render Postgres database from the terminal?

Use `render psql <database-id> -c "SELECT ..."` to run a single query without opening an interactive session. Add `-o json` for machine-readable output or `-o text -- --csv` to get CSV-formatted results through psql passthrough flags.

Why does the Render CLI hang or prompt in my CI job?

The CLI defaults to interactive mode in TTY environments and asks for confirmation on destructive actions. Always pass `--confirm` to skip prompts and `-o json` or `-o text` for non-interactive output, or set `RENDER_OUTPUT=json` globally.

What do I do when my Render CLI token expires?

Re-run `render login` to open the browser and generate a new CLI token, which is saved to `~/.render/cli.yaml`. For long-lived automation, switch to a `RENDER_API_KEY` environment variable since API keys do not expire.