render-automation
Automate Render cloud deployments and services
También disponible en: sickn33
Manual Render deployments and service management consume valuable DevOps time. This skill automates Render platform operations through MCP tools for services, deployments, and projects.
Descargar el ZIP de la skill
Subir en Claude
Ve a Configuración → Capacidades → Skills → Subir skill
Activa y empieza a usar
Pruébalo
Usando "render-automation". List all Render services with type filter for web_service
Resultado esperado:
Found 3 web services: api-production (srv-abc123), frontend-prod (srv-def456), worker-main (srv-ghi789). All services currently live with recent deployments.
Usando "render-automation". Trigger deployment for service srv-abc123 with cache clear
Resultado esperado:
Deployment triggered successfully. Deploy ID: dep-d2mqkf9r. Status: build_in_progress. Started at 2026-02-24T23:15:00Z.
Auditoría de seguridad
SeguroAll static analysis findings are false positives. The SKILL.md file is documentation only - backticks are markdown formatting for code examples, not executable Ruby/shell commands. No actual security risks detected.
Puntuación de calidad
Lo que puedes crear
DevOps Engineer
Trigger deployments after code reviews and monitor progress without leaving the chat interface
Full-Stack Developer
List services by name, check deployment status, and manage projects during development cycles
Platform Team
Automate routine Render operations across multiple services and environments
Prueba estos prompts
List all my Render services and show me which ones are web services versus static sites.
Find the service named 'api-production' and trigger a new deployment with cache clearing enabled.
Check the status of deployment 'dep-xxxx' on service 'srv-yyyy' and tell me when it reaches live status.
Deploy my 'frontend-prod' service, then poll the deployment status every 20 seconds until it completes. Report any failures with error details.
Mejores prácticas
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas before any operations
- Use 10-30 second intervals when polling deployment status to avoid rate limits
- Resolve service names to IDs via RENDER_LIST_SERVICES before trigger operations
Evitar
- Rapid polling of deployment status without delays causes rate limit errors
- Assuming service IDs without verification leads to wrong service deployments
- Ignoring deployment terminal states and continuing to poll indefinitely
Preguntas frecuentes
What is required to use this skill?
How do I find my service ID?
Are deployments synchronous or asynchronous?
What deployment statuses should I expect?
How does pagination work for listing services?
What happens if a deployment fails?
Detalles del desarrollador
Autor
sickn33Licencia
MIT
Repositorio
https://github.com/sickn33/antigravity-awesome-skills/tree/main/web-app/public/skills/render-automationRef.
main
Estructura de archivos
📄 SKILL.md