AutoGineer
Generated banner for Render CLI
Generated logo for Render CLI

Render CLI

RenderOfficialCreated by Render

  • Skill
  • Tool integration
  • Cloud and DevOps
  • MIT
  • No issues found
Download ZIP

From the author

Installs and uses the Render CLI for deploys, logs, SSH, psql, Blueprint validation, and automation. Use when the user needs to run Render CLI commands, script deploys in CI/CD, authenticate with an API key, query services non-interactively, or troubleshoot CLI auth issues. Trigger terms: render CLI, render login, render deploys, render logs, render ssh, render psql, render blueprints validate, render skills, RENDER_API_KEY, non-interactive, CI/CD deploy.
— the description by Render

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Render CLI skill provides a comprehensive interface for interacting with the Render platform. It supports both interactive terminal usage for developers and non-interactive scripting for CI/CD automation. The skill covers essential operational tasks including service management, database access via psql, log streaming, SSH connectivity, and Blueprint validation. It emphasizes secure authentication practices and reliable, machine-readable output formats for automated workflows.

What it does

  • Deploys services and manages deployment lifecycles
  • Streams real-time logs from running services
  • Provides direct psql access to Render Postgres databases
  • Enables SSH access to service instances and ephemeral shells
  • Validates render.yaml Blueprint configurations
  • Facilitates non-interactive automation in CI/CD environments

When to use it

  • When you need to automate service deployments in a CI/CD pipeline
  • When troubleshooting service behavior via logs or SSH
  • When performing database operations on Render Postgres
  • When validating infrastructure-as-code Blueprint files locally
  • When managing Render resources without using the web dashboard

Advantages

  • Supports machine-readable output formats like JSON for reliable scripting
  • Enables non-interactive operations with global flags
  • Provides consistent access to logs and SSH for debugging
  • Integrates seamlessly into standard CI/CD workflows
  • Allows for secure authentication using API keys

Usage examples

“Deploy my web service srv-123 and wait for it to finish.”
The agent executes 'render deploys create srv-123 --wait --confirm -o json' to trigger the deployment and monitor its status.
“Show me the logs for my service srv-abc.”
The agent runs 'render logs -r srv-abc' to stream the latest logs from the specified service.
“Validate my render.yaml file.”
The agent executes 'render blueprints validate' to check the configuration file for errors.
“Run a SQL query on my database db-xyz.”
The agent uses 'render psql db-xyz -c "SELECT * FROM users;" -o json' to execute the query and return the results in JSON format.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/render-oss/render-cli/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip render-cli.zip -d .agents/skills

Documentation by Render

Render CLI

The Render CLI manages services, databases, and deployments from the terminal. Supports interactive use, non-interactive scripting, and CI/CD automation.

Before installing, authenticating, selecting a workspace, or running commands, read references/render-access.md for the current access and command-discovery workflow.

When to Use

  • Deploying a service from the terminal or CI/CD

  • Tailing logs in real time

  • Opening psql to a Render Postgres database

  • SSHing into a running service or launching an ephemeral shell

  • Validating a render.yaml Blueprint

  • Scripting Render operations in CI/CD pipelines

  • Installing agent skills for AI coding tools

Command Reference

Use the installed CLI help or generated command reference as directed by references/render-access.md for the exact command surface and flags. The patterns below cover common operational workflows.

Deploy patterns
# Deploy and wait for completion (exits non-zero on failure)
render deploys create srv-xxx --wait --confirm -o json

# Deploy a specific commit
render deploys create srv-xxx --commit abc123 --wait --confirm

# Deploy a specific Docker image
render deploys create srv-xxx --image ghcr.io/org/app:v1.2.3 --wait --confirm
Database queries
# Single query, JSON output
render psql db-xxx -c "SELECT NOW();" -o json

# CSV output via psql passthrough
render psql db-xxx -c "SELECT id, email FROM users;" -o text -- --csv

CI/CD Example (GitHub Actions)

name: Deploy to Render
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Install Render CLI
        run: |
          curl --fail-with-body --silent --show-error --location \
            https://raw.githubusercontent.com/render-oss/cli/refs/heads/main/bin/install.sh \
            --output /tmp/install-render-cli.sh
          sudo sh /tmp/install-render-cli.sh
          render --version
      - name: Deploy
        env:
          RENDER_API_KEY: ${{ secrets.RENDER_API_KEY }}
        run: render deploys create ${{ secrets.RENDER_SERVICE_ID }} --wait --confirm -o json

If reproducible builds require a pinned CLI, select a currently supported release and verify its asset name in the current release documentation instead of copying a version from this skill.

Local Config

Config file: ~/.render/cli.yaml

Override the configuration directory with RENDER_CLI_CONFIG_DIR. RENDER_CLI_CONFIG_PATH is a legacy file-level override retained for compatibility and is scheduled for deprecation.

Common Mistakes

MistakeFix
Deploying without --wait in CIAdd --wait so the job fails on deploy failure

References

DocumentContents
references/render-access.mdCurrent CLI authentication, workspace, documentation, output, and authorization workflow
references/command-cheatsheet.mdCommon operational command examples and scripting patterns

Related Skills

  • render-deploy — End-to-end deploy flows, MCP operations, Dashboard deeplinks

  • render-blueprints — render.yaml authoring and validation

  • render-postgres — Database connections, render psql usage

  • render-debug — Using render logs and render ssh for troubleshooting

<!-- shared:documentation-retrieval -->

Current documentation retrieval

Whenever this skill directs you to consult current Render documentation:

  1. Retrieve the linked Markdown document directly with an available URL-fetching tool or HTTP client, such as curl. Do not substitute web-search summaries for the document.

  2. Confirm that retrieval succeeded and returned the expected document, then read its contents. Saving a file or printing its path is not sufficient.

  3. If the request fails or your tool cannot read the Markdown response, open and read the linked HTML version instead.

  4. If neither version can be retrieved, disclose that the current reference is unavailable and follow any topic-specific fallback in the skill. Use bundled guidance only for stable constraints, and do not guess at changeable platform details.

When a task requires multiple references, apply this workflow to each one and distinguish the documents you verified from those that remain unavailable.

<!-- /shared:documentation-retrieval -->

Files

references/render-access.md

<!-- shared:render-access -->

Accessing Render

Prefer the hosted Render MCP server for structured access to Render resources when its tools are available. Use the Render CLI when MCP is unavailable or does not support the required operation, and use the Render Dashboard or API for capabilities exposed by neither. Do not assume that a remembered MCP tool or CLI command is still available; inspect the tools in the current environment or consult the current documentation.

The hosted Render MCP server uses streamable HTTP at:

https://mcp.render.com/mcp

Official Render plugins and connectors can authenticate MCP with browser-based OAuth. Manual and non-interactive configurations can use a Render API key as a bearer token. Never write an API key or OAuth token into a repository, skill, command output, chat response, or log. Prefer the client's supported secret storage or environment-variable mechanism. If a client requires a credential in local configuration, keep that file out of version control and restrict access to it.

Treat MCP responses as potentially sensitive even when the server attempts to minimize credential exposure. Request connection strings, credentials, secret environment variables, or other sensitive fields only when the task requires them. Do not repeat sensitive values in the response or persist them in files or logs.

Before configuring or troubleshooting MCP, fetch the current setup and capability reference:

Using the documentation-retrieval workflow in the root SKILL.md, retrieve and read the Markdown reference or its HTML version.

Read the relevant client setup, supported-actions, and limitations sections. Prefer the hosted server unless the user's environment requires a local MCP server. After installing, updating, or reconfiguring an MCP integration, reload the client as required and verify the connection with a read-only operation such as listing services.

Most MCP operations and Render CLI commands that access Render resources are scoped to an active workspace. Check the selected workspace before reading or changing resources. If no workspace is selected—or if the intended workspace is ambiguous—list the available workspaces and have the user identify the correct one. Do not silently switch workspace context or infer it from a resource name. Commands for authentication, help, CLI configuration, and workspace discovery or selection do not require an already selected workspace.

For interactive CLI use, authenticate with render login. For automation, use a securely stored RENDER_API_KEY; an API key takes precedence over a saved CLI token. Verify CLI access and the active workspace with read-only commands before operating on resources:

render whoami --output json
render workspace current --output json

For CLI installation, authentication, workspace setup, and usage patterns, fetch the current CLI overview:

Using the documentation-retrieval workflow in the root SKILL.md, retrieve and read the Markdown reference or its HTML version.

For exact command syntax and flags, prefer the help text from the installed CLI because it matches the version being used:

render help <command>

The published CLI command reference is generated automatically from the CLI's help text. Use it to browse the full command surface or when the CLI is not installed:

Using the documentation-retrieval workflow in the root SKILL.md, retrieve and read the Markdown reference or its HTML version.

When an agent or automation invokes the CLI, select a non-interactive output format such as --output json, --output yaml, or --output text so results can be inspected reliably. The global --confirm flag skips confirmation prompts; use it for a mutating command only after that mutation is authorized. It is an execution convenience, not permission to perform the action.

Authentication establishes access; it does not establish user authorization for every available action. Use read-only discovery to resolve workspace, resource identity, and current state before a mutation. Perform changes only when they are within the user's requested scope, and retain normal approval requirements for consequential operations such as creation, configuration changes, deploys, restarts, scaling, or deletion.

When authentication or connectivity fails, report which access path failed, preserve the underlying error without exposing credentials, and either use an available supported fallback or explain what the user must configure before the task can continue.

<!-- /shared:render-access -->

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an API key

The author says: Render CLI v2.7.0+ (Homebrew, Linux/macOS, direct download)

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Render
Publisher
Render (Official)
Source
render-oss/skills · skills/render-cli · commit b985a63
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Render or Render.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download render-cli.zip