Back to catalog / Integrations
Render deployment: choose Git Blueprint or image Dashboard path first
Choose Blueprint or direct creation based on source and infrastructure ownership.
Skills
Inspect the repository, runtime, service dependencies, and Git remote. Without a remote, Git-backed Blueprint/MCP flows cannot proceed; ask whether to push or use the Dashboard image path. Confirm whether Render should provision all dependencies or only the app. Choose a `render.yaml` multi-service Blueprint or direct MCP creation. Because deploy creates billable resources, present service types, region, instance, and persistent storage scope and obtain authorization; config-only requests must not apply.
Permissions
Prerequisites
- Deploy a Git-backed app to Render using a Blueprint or direct service creation.
Permissions
- Can create billable Render services/databases/cron resources and connect repositories.
Limitations
Git deploy requires a pushed remote; confirm source and infrastructure ownership before creating resources.
Pinned upstream source
- Repository
- openai/skills
- File path
- skills/.curated/render-deploy/SKILL.md
- Pinned commit
49f948faa9258a0c61caceaf225e179651397431- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Compatible tools
Render MCP tools · Render Dashboard · `render.yaml` Blueprints
Main topic
Turn ecommerce campaign materials into a reviewable weekly brief