deploy-on-render_skill

Overview

This skill deploys and operates applications on Render using Blueprints (render.yaml), the Render Dashboard deeplink, or the Render API. It mirrors the Codex render-deploy flow: analyze the repo, generate/validate a Blueprint, commit and push, provide a one-click Dashboard deeplink, and optionally trigger or verify deploys via the API or mcporter.

How this skill works

The skill inspects the codebase to detect runtime, build and start commands, and required services (web, static, worker, cron, Postgres, Key Value). It generates or updates a render.yaml at the repo root, validates the Blueprint (CLI or Validate Blueprint API), and guides the user to commit/push. If RENDER_API_KEY is present it can call Render APIs or mcporter to create services or verify deploy status; otherwise it provides a deeplink for a one-click deploy in the Dashboard.

When to use it

• You want to deploy, host, or publish an app on Render from a Git repo.
• You need a render.yaml Blueprint created, edited, or validated for deployment.
• You must add or configure services: web, static, worker, cron, Postgres, or Key Value.
• You want a one-click Dashboard deeplink to create services from the Blueprint.
• You have RENDER_API_KEY and want the agent to trigger or verify deploys via API or mcporter.

Best practices

• Keep render.yaml at the repository root and validate with the Render CLI or Validate Blueprint API before pushing.
• Never commit secrets: use sync: false for secrets and prompt users to add them in the Dashboard.
• Ensure a Git remote is pushed (HTTPS) so the Dashboard deeplink can connect to the repo.
• Sanitize and quote any user-provided values when writing env vars to avoid injection.
• Prefer runtime over deprecated env keys; use services + fromService for Key Value and Postgres references.

Example use cases

• Generate a render.yaml for a Node or Python web app, add a Postgres database, and produce the Dashboard deeplink for one-click deploy.
• Convert a monorepo service into a Render Blueprint with rootDir and buildFilter settings and validate it before push.
• Create a full-stack Blueprint (web + Postgres + Key Value) and either trigger create via API when RENDER_API_KEY is set or provide the deeplink.
• Add a cron job or background worker service to an existing Blueprint and configure schedules, build, and start commands.
• Validate an existing render.yaml and run post-deploy checks via the Render API to verify health and deploy status.