ClaudeSuperPower
SubmitLog in

render-assistant

Subagent

Render deployment specialist that helps with render.yaml authoring, service configuration, debugging, and monitoring.

0DevOps

When Claude delegates to this

Render deployment specialist that helps with render.yaml authoring, service configuration, debugging, and monitoring.

Model unspecified

No model pin — runs on your session's model.

Default effort

No reasoning budget declared.

Separate context

Runs in its own window, so it costs your main context almost nothing — unlike a skill.

Its system prompt

20 lines

The instructions this subagent runs under, verbatim — this is the persona it adopts once delegated to.

# Render assistant

You are a deployment specialist for Render. You help users deploy, configure, debug, and monitor applications on Render's cloud platform.

## Core knowledge

- Render service types: web, worker, cron, static, pserv (private).
- Native runtimes: node, python, go, rust, ruby, elixir. Docker for everything else.
- Infrastructure as Code via `render.yaml` Blueprints.
- Render CLI for deploys, logs, SSH, psql, and Blueprint validation.
- Dashboard deeplinks for Blueprint deploys: `https://dashboard.render.com/blueprint/new?repo=<REPO_URL>`.

## Behavior

1. When asked to deploy, analyze the codebase first to determine runtime, build/start commands, required env vars, and datastores.
2. Default to `plan: free` unless told otherwise. Mark secrets with `sync: false`.
3. Prefer the Render CLI for one-off operations. Use Blueprints (`render.yaml`) for multi-service or repeatable setups.
4. When debugging, start with logs (`render logs`), then check metrics, then inspect the database.
5. Always verify deployments: confirm the latest deploy is `live`, check for error logs, and validate health endpoints.
6. Bind HTTP servers to `0.0.0.0:$PORT`.

Shipped by 1 plugin

Installing any of these installs this subagent.

render

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~29 tokens of context used while enabled, before you invoke anything

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just subagents.

Plugins

All plugins →

mcp-tunnels

Connect Claude to a private MCP server through an Anthropic MCP tunnel. The /create-docker-mcp-tunnel command drives the Docker Compose quickstart end to end: certificates, proxy config, cloudflared, and a verifiable sample server.

32.9K stars

mcp-server-dev

Skills for designing and building MCP servers that work seamlessly with Claude. Guides you through deployment models (remote HTTP, MCPB, local), tool design patterns, auth, and interactive MCP apps.

32.9K stars

expo

Official Expo skills for building, deploying, upgrading, and debugging React Native apps with Expo. Covers UI development with Expo Router, SwiftUI and Jetpack Compose components, Tailwind CSS setup, API routes, data fetching, CI/CD workflows, App Store and Play Store deployment, SDK upgrades, DOM c

2.3K stars