skilld
All skills
openai avatar

/render-deploy

@bf9e226 official
by openaiopenai/skills28k stars
1,891

Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.

Ask your Agent

Use this Skill: https://skilld.dev/gh/openai/skills/render-deploy

This session only. Nothing lands on disk.

referencestroubleshooting-basics.md

≈341 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Basic troubleshooting (deploy-time and startup)

Use this when a deploy fails, the service crashes on start, or health checks time out. Keep fixes minimal and redeploy after each change.

1) Classify the failure

  • Build failure: errors in build logs, missing dependencies, build command issues.
  • Startup failure: app exits quickly, crashes, or cannot bind to $PORT.
  • Runtime/health failure: service is live but health checks fail or 5xx errors.

2) Quick checks by class

Build failure

  • Confirm the build command is correct for the runtime.
  • Ensure required dependencies are present in package.json, requirements.txt, etc.
  • Check for missing build-time env vars.

Startup failure

  • Confirm the start command and working directory.
  • Ensure port binding is 0.0.0.0:$PORT.
  • Check for missing runtime env vars (secrets, DB URLs).

Runtime/health failure

  • Verify the health endpoint path and response.
  • Confirm the app is actually listening on $PORT.
  • Check database connectivity and migrations.

3) Map error signatures to fixes

Use error-patterns.md for a compact catalog of common log messages.

4) If still blocked

Gather the latest build logs and runtime error logs, then consider the optional render-debug skill for deeper diagnostics (metrics, DB checks, expanded patterns).

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill includes some configuration sequences for setting up the Render deployment pipeline, such as downloading the official Render CLI installation script via a shell pipe. While running piped scripts warrants standard security consideration, the source belongs to the vendor's verified repository infrastructure. All other operations match standard deployment behaviors.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    19/19 files flagged

  • ZeroLeaks5mo

    1 finding · Score: 82/100

Provenance

Signed by skilld at bf9e226. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Activeupdated 8 months ago

Topics

README badge

README badge for openai/skills/render-deploy

What it does

Analyzes codebases and generates render.yaml Blueprint files to deploy applications to Render's cloud platform using Git-backed services. Covers both single-service deployments via MCP tools and multi-service Infrastructure-as-Code setups, with support for databases, workers, and cron jobs.

Generated from the current SKILL.md.

Frequently asked

Does this skill support Docker image deployments?
Partially. Render supports prebuilt Docker images, but this skill covers only Git-backed flows. If you want to deploy a Docker image directly, use the Render Dashboard or API. You can also use a Blueprint with `runtime: image` if you have a Git repo containing the render.yaml file.
What Git providers does this skill support?
GitHub, GitLab, and Bitbucket. The repository must be pushed to one of these providers before deploying.
When should I use Blueprint vs Direct Creation?
Use Blueprint for multi-service apps, databases, cron jobs, or infrastructure-as-code workflows. Use Direct Creation (MCP) for single services with no attached databases or workers.
Do I need the Render CLI installed?
MCP tools are preferred and don't require CLI installation. The CLI is optional but recommended for validating render.yaml before deployment.
What if I don't have a Git remote yet?
You must create and push a Git remote to GitHub, GitLab, or Bitbucket before deploying. For Docker image deployments, use the Render Dashboard instead.

Generated from the current SKILL.md. These answers refresh after source changes.