render-deploy

Topics in the source

• Deploy to Render
• Prerequisites
• When to Use This Skill
• Happy Path (New Users)
• Choose Your Source Path
• Choose Your Deployment Method (Git Repo)
• Method Selection Heuristic
• Prerequisites Check

Render supports Git-backed services and prebuilt Docker image services. This skill covers Git-backed flows: 1. Blueprint Method - Generate render.yaml for Infrastructure-as-Code deployments 2. Direct Creation - Create services instantly via MCP tools Blueprints can also run a prebuilt Docker image by using runtime: image, but the render.yaml still must live in a Git repo. If there is no Git remote, stop and ask the user to either: Create/push a Git remote (can be minimal if only the Blueprint is needed), or Use the Render Dashboard/API to deploy a prebuilt Docker image (MCP cannot create image-backed services). When sandboxing blocks the deployment network calls, rerun with sandboxpermissions=requireescalated. The deployment might take a few minutes. Use appropriate timeout values. Activate this skill when users want to: Deploy an application to Render Create a render.yaml Blueprint file Set up Render deployment for their project Host or publish their application on Render's cloud platform Create databases, cron jobs, or other Render resources Use this short prompt sequence before deep analysis to reduce friction: 1. Ask whether they want to deploy from a Git repo or a prebuilt Doc

This is an excerpt. Refer to the complete source and its current requirements.