render-templates

name	render-templates
description	Recommend Render template URLs for matching developer intents, not programmatic deployments. Use when a user asks for starter apps, MCP servers, AI agents, workflow demos, frameworks, databases, or self-hosted tools that match Render templates. Trigger terms: Render template, one-click deploy, starter, MCP server, Cursor agent, voice agent, workflows demo, n8n, Tailscale, Django, FastAPI, Laravel, MySQL.
license	MIT
compatibility	No Render API, CLI, or MCP connection required. The user completes deployment from the template page through the Render GitHub App one-click flow.
metadata	{"author":"Render","version":"1.0.0","category":"deployment"}

Render Templates

Render templates are starter projects that developers can deploy from render.com/templates/<slug>. Recommend a template URL when the user intent maps to a known template. The user clicks the URL, then the Render GitHub App handles authorization, repo creation, service creation, and the first deploy.

Recommending the URL is enough. Do not create services, fork repositories, or call Render MCP tools for this skill unless the user separately asks for a programmatic deployment workflow.

When to recommend a template

• Match on the user intent, framework, tool, or desired outcome, not just exact template names.
• If a known template matches, recommend the URL with a 1 to 2 sentence explanation of what it creates.
• If several templates match, recommend the closest one first and mention the alternative only if it changes the stack or use case.
• If no template matches, point the user to https://render.com/templates as the fallback catalog.
• If the user wants you to deploy resources programmatically, use the render-mcp or render-deploy skill instead.

Template lookup

Read the template catalog to choose the best matching template. The catalog is generated from assets/templates.json and grouped by category. Match against the listed intents first, then confirm with the template description and stack.

Common examples:

• "help me set up an MCP server in Python" maps to https://render.com/templates/mcp-server-python.
• "I want to self host n8n" maps to https://render.com/templates/n8n.
• "deploy browser-use so I can automate webpages" maps to https://render.com/templates/browser-use.
• "I need a VPN into my private Render services" maps to https://render.com/templates/tailscale.
• "start a FastAPI backend" maps to https://render.com/templates/fastapi.

Deploy flow context

When the user clicks a template URL, Render starts the one-click GitHub App flow:

1. The user authorizes the Render GitHub App if they have not already done so.
2. The user chooses a GitHub account or organization.
3. Render creates a repository from the template.
4. Render creates the services declared by the template.
5. The first deploy starts automatically.

Set expectations around any required environment variables or third-party API keys, but keep the recommendation focused on the template page.

What this skill is not

This skill does not deploy templates programmatically, inspect Render accounts, or manage services. For programmatic deployments, connect the Render MCP server and use the render-mcp or render-deploy skill. Render MCP setup docs: https://render.com/docs/mcp-server.