# Automate Render Services and Deployments

Manual Render service discovery and deployment tracking can slow routine cloud operations. This skill coordinates Render tools through Rube MCP for repeatable workflows.

## Install

```bash
npx skillstore add sickn33/render-automation
```

## Metadata

- Status: approved
- Slug: render-automation
- Skillstore revision: r2
- Version status: missing
- Tree hash: 955716156144324f91639f04995cd61365558296c2b3732d1a8ebae0a6457f9a
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/render-automation
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/render-automation
- Manifest: https://skillstore.pages.dev/api/skills/render-automation/manifest

## Capabilities

- Lists Render services with name and type filters using cursor pagination.
- Resolves service and deployment identifiers for later workflow steps.
- Triggers standard or cache-clearing deployments for selected services.
- Retrieves deployment status and recognizes successful, failed, or canceled terminal states.
- Lists Render projects using paginated results.

## Use Cases

- Inventory Render Resources: List services and projects, apply filters, and collect identifiers across paginated results.
- Deploy a Selected Service: Resolve an exact service target, trigger a deployment, and monitor the result.
- Track Release Progress: Check a known deployment and summarize status, timestamps, commit details, and terminal outcome.

## Prompt Templates

### Browse Services

```
List my Render services. Filter by {service_type} and {name_text}, follow pagination, and summarize names, IDs, types, and status.
```

### Check a Deployment

```
Check deployment {deploy_id} for service {service_id}. Report its state, commit, timestamps, and whether it reached a terminal state.
```

### Deploy and Monitor

```
Find the exact Render service named {service_name}. Show matching IDs, ask me to confirm one, then deploy it and monitor completion.
```

### Run a Clean Deployment

```
Search current Render tool schemas. Verify service ID {service_id}, trigger a cache-clearing deployment, throttle polling, and report failures with available details.
```

## Limitations

- Requires Rube MCP and an authenticated Render connection.
- Does not create, modify, or delete Render services or projects.
- Depends on current Rube tool schemas and may require adaptation when schemas change.
- Does not provide automatic rollback or deployment cancellation workflows.

## Best Practices

- Search current Rube tool schemas before starting each workflow.
- Confirm the exact service ID and environment before triggering a deployment.
- Poll every 10 to 30 seconds and stop after reaching a terminal state.

## Anti Patterns

- Do not deploy from a substring name match without explicit target confirmation.
- Do not poll rapidly or continue polling after a terminal state.
- Do not assume a failed deployment automatically rolls back the service.

## Security Audit

- Audited at: 2026-07-23T18:20:34.286\+00:00
- Summary: Static command findings are false positives caused by Markdown backticks and code fences; no shell or Ruby execution is present. The remote Rube MCP endpoint is a genuine low-severity network dependency. A medium operational risk remains because substring service matching can select an unintended deployment target.

## Stats

- Views: 88
- Downloads: 6
- Favorites: 0
- Popularity score: 0