Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.
62
46%
Does it follow best practices?
Impact
89%
1.32xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/render-automation/SKILL.mdDeploy and monitor workflow
RUBE_SEARCH_TOOLS first
0%
100%
Connection check step
0%
100%
LIST_SERVICES before deploy
100%
100%
srv- ID format
100%
100%
dep- ID format
100%
100%
Async polling loop
100%
100%
Polling interval
100%
100%
Terminal status values
100%
100%
Full status enum
100%
100%
No auto-rollback on failure
100%
100%
Response data key
0%
100%
Concurrent deploy caveat
100%
100%
Service listing and pagination
RUBE_SEARCH_TOOLS first
0%
100%
Connection verification
0%
100%
Cursor pagination loop
100%
100%
Limit set to 100
100%
100%
web_service enum value
100%
100%
background_worker enum value
100%
100%
cron_job enum value
100%
100%
static_site and private_service enums
100%
100%
Substring name filter
100%
100%
srv- ID format
0%
0%
LIST_PROJECTS usage
0%
0%
Rate limit awareness
0%
0%
Cache-clear deployment and status handling
RUBE_SEARCH_TOOLS first
0%
50%
RUBE_MANAGE_CONNECTIONS step
0%
57%
clearCache parameter
100%
100%
clearCache trade-off
100%
100%
LIST_SERVICES for ID resolution
37%
100%
All 8 deploy statuses
60%
100%
live = success
100%
100%
build_failed and update_failed as errors
100%
100%
No rollback on failure
100%
100%
data key in response
12%
100%
Polling interval range
100%
100%
dep- ID format
100%
100%
3069d33
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.