Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.
60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Deploy 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%
Without context: $0.4163 · 2m 10s · 19 turns · 92 in / 6,781 out tokens
With context: $0.3294 · 1m 31s · 15 turns · 175 in / 4,638 out tokens
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%
Without context: $0.2851 · 1m 26s · 14 turns · 70 in / 4,673 out tokens
With context: $0.4769 · 1m 59s · 23 turns · 31 in / 5,876 out tokens
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%
Without context: $0.3056 · 1m 39s · 14 turns · 18 in / 5,310 out tokens
With context: $0.2538 · 1m 8s · 11 turns · 14 in / 3,546 out tokens
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.