$ ~/registry/skill/openai-curated-render-deploy

SKILL

render-deploy

Name: render-deploy
Author: OpenAI

Analyze codebases and generate Render configs to deploy apps to the cloud.

Stars

★ 23,132

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 22.0k

Summary

This appears to be an open-source, highly adopted prompt-only deployment skill with no declared secrets or fixed remote endpoints. Overall risk is low, though any deployment or sandbox-escalation flow mentioned in the docs should only be used when the underlying tools and target platform are trusted.

CredentialsLow risk

The materials and objective checks indicate that this skill requires no secrets or environment variables. It does not ask for API tokens, cloud credentials, or other sensitive authentication data, so direct credential exposure appears low.

Network egressLow risk

The system checks show no declared remote endpoint, and the skill is marked prompt-only. Although the README discusses deployment to Render and possible network calls, the material suggests guidance rather than the skill itself performing fixed outbound data transfers.

Code executionCaution

The README explicitly mentions Direct Creation via MCP and suggests rerunning with `sandbox_permissions=require_escalated` when sandboxing blocks deployment calls. This indicates the intended workflow may invoke underlying tools for deployment actions or request elevated permissions. That is a normal capability for deployment tooling, with no specific red flag beyond the stated purpose.

Data accessCaution

The skill analyzes codebases and generates `render.yaml`, which implies expected access to project/repository contents and possible writing of deployment configuration files. This is a normal access scope for its stated function, and the materials do not show obvious overreach.

Supply chainLow risk

The source is the open-source openai/skills repository on GitHub with high community adoption (about 22k stars), providing strong auditability and source credibility. Although the license is unspecified and maintenance status is unknown, there is no visible red flag such as closed-source exfiltration, impersonation, or clear supply-chain abuse.

Recommendations

Only follow the deployment or escalation guidance after confirming the underlying MCP tools and Render workflow are trusted.
If repository reading or `render.yaml` generation is needed, use a least-privilege environment and review file changes first.
Manually review any `require_escalated` scenario mentioned in the README to avoid unnecessary high-privilege execution.
Before deployment, verify which Render resources, repo bindings, and public links will be created.

Audited by: gpt-5.4 · 2026-06-16

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "render-deploy" skill from askskill:
1. Download https://raw.githubusercontent.com/openai/skills/main/skills/.curated/render-deploy/SKILL.md
2. Save it as ~/.claude/skills/render-deploy/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Deploy to Render

Render supports Git-backed services and prebuilt Docker image services.

This skill covers Git-backed flows:

Blueprint Method - Generate render.yaml for Infrastructure-as-Code deployments
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.

When to Use This Skill

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

Happy Path (New Users)

Use this short prompt sequence before deep analysis to reduce friction:

Ask whether they want to deploy from a Git repo or a prebuilt Docker image.
Ask whether Render should provision everything the app needs (based on what seems likely from the user's description) or only the app while they bring their own infra. If dependencies are unclear, ask a short follow-up to confirm whether they need a database, workers, cron, or other services.

Then proceed with the appropriate method below.

Choose Your Source Path

Git Repo Path: Required for both Blueprint and Direct Creation. The repo must be pushed to GitHub, GitLab, or Bitbucket.

Prebuilt Docker Image Path: Supported by Render via image-backed services. This is not supported by MCP; use the Dashboard/API. Ask for:

Image URL (registry + tag)
Registry auth (if private)
Service type (web/worker) and port

If the user chooses a Docker image, guide them to the Render Dashboard image deploy flow or ask them to add a Git remote (so you can use a Blueprint with runtime: image).

Choose Your Deployment Method (Git Repo)

Both methods require a Git repository pushed to GitHub, GitLab, or Bitbucket. (If using runtime: image, the repo can be minimal and only contain render.yaml.)

Method	Best For	Pros
Blueprint	Multi-service apps, IaC workflows	Version controlled, reproducible, supports complex setups
Direct Creation	Single services, quick deployments	Instant creation, no render.yaml file needed

Method Selection Heuristic

Use this decision rule by default unless the user requests a specific method. Analyze the codebase first; only ask if deployment intent is unclear (e.g., DB, workers, cron).

Use Direct Creation (MCP) when ALL are true:

Single service (one web app or one static site)
No separate worker/cron services
No attached databases or Key Value
Simple env vars only (no shared env groups) If this path fits and MCP isn't configured yet, stop and guide MCP setup before proceeding.

Use Blueprint when ANY are true:

Multiple services (web + worker, API + frontend, etc.)
Databases, Redis/Key Value, or other datastores are required
Cron jobs, background workers, or private services
You want reproducible IaC or a render.yaml committed to the repo
Monorepo or multi-env setup that needs consistent configuration

If unsure, ask a quick clarifying question, but default to Blueprint for safety. For a single service, strongly prefer Direct Creation via MCP and guide MCP setup if needed.