render-deploy
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. Do NOT use for deploying to Vercel, Netlify, or Cloudflare (use their respective skills).
npx skills add tech-leads-club/agent-skills --skill render-deploy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Deploy to Render by analyzing a codebase to determine framework/runtime, then generate a render.yaml Blueprint or enable direct service creation via MCP tools. Provides a Render Dashboard deeplink to proceed with deployment. Supports Git-backed flows (Blueprint or Direct Creation) and can utilize prebuilt Docker images via render.yaml, requiring a Git repository presence. If no Git remote exists, it instructs the user to create/push a remote or use Docker image deployment through the Dashboard/API. It guides through prerequisites, authentication setup, workspace context, and a two-method deployment approach (Blueprint for IaC/multi-service or Direct Creation for single services). It emphasizes not using this for Vercel, Netlify, or Cloudflare, and outlines a detailed step-by-step process for blueprint creation, validation, committing, and deploying via the Dashboard, including secrets handling and environment variables.
How it works
- Determine deployment path: Git-backed Blueprint or Direct Creation based on codebase analysis; also supports prebuilt Docker image with render.yaml in the Git repo.
- Generate a render.yaml blueprint with a services section (type, name, runtime, buildCommand, startCommand) and envVars, plus optional databases; set plan: free by default.
- Validate configuration via CLI when available: authenticate, validate, commit, push, and open Render Dashboard via a blueprint deeplink.
- Provide a dashboard deeplink formatted as https://dashboard.render.com/blueprint/new?repo=<REPOSITORY_URL> after ensuring render.yaml is in the repository.
- Provide step-by-step guidance for authentication, workspace context, and deployment verification using MCP or CLI depending on tool availability.
- For single-service deployments, offer Direct Creation path and MCP setup prompts.
When to use it
Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform, including creating render.yaml, deploying to Render, or provisioning resources like databases or cron jobs. Do not use for Vercel, Netlify, or Cloudflare deployments.
What it can touch
- Files: render.yaml is created/edited in the user’s Git repository.
- Tools: MCP (preferred for single-service), render CLI for validation, Git, and the Render Dashboard.
- Secrets handling via envVars with sync: false elements to be filled in the Dashboard; guidance for API keys is provided but keys themselves are never embedded here.
Caveats
- Requires a Git remote; if absent, user must create/push a remote or switch to Docker image deployment.
- API keys and secrets must be handled via environment variables; never paste keys directly in chat or code examples.
- Sandbox permissions may be needed for network calls; use sandbox_permissions=require_escalated when necessary.
- Deployment may take several minutes; respect timeout values.
# Deploy to Render 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). ## Prerequisites - When sandboxing blocks the deployment network calls, rerun with `sandbox_permissions=require_escalated`. - The deployment might take a few minutes. Use appropriate timeout values. ## Security Requirements for API Keys and Secrets **CRITICAL - You must protect user credentials:** When handling Render API keys or any secrets: 1. **NEVER ask users to paste API keys directly in chat** - Instead, instruct them to set environment variables: ```bash export RENDER_API_KEY="rnd_xxxxx" ``` 2. **NEVER include actual
- Prerequisites
- Security Requirements for API Keys and Secrets
- When to Use This Skill
- Happy Path (New Users)
- Choose Your Source Path
- Choose Your Deployment Method (Git Repo)
- Method Selection Heuristic
- Prerequisites Check
- Cursor
- Claude Code
- Other Tools
- Workspace Selection
- Blueprint Workflow
- Step 1: Analyze Codebase
export RENDER_API_KEY="rnd_xxxxx" git remote -v render --version claude mcp add --transport http render https://mcp.render.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>" Check if user is logged in (use -o json for non-interactive mode) render whoami -o json render workspace current -o json render whoami -o json # Ensure CLI is authenticated (won't always prompt) render blueprints validate git add render.yaml
What does the render-deploy skill do?
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. Do NOT use for deploying to Vercel, Netlify, or Cloudflare (use their respective skills).
How do I install it?
Run `npx skills add tech-leads-club/agent-skills --skill render-deploy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.