360 Secure SkillHub
360 安全技能中心

Render

该 Skill 借助 oo CLI 调用 OOMOL 的 render 连接器管理 Render 平台资源，凭据由服务端注入，用户不直接接触令牌。支持查询当前用户、服务、部署和工作区，以及触发部署、重启、暂停/恢复服务和回滚部署，写操作与破坏性操作需先向用户确认。

oomol
oomol
热度 54.30
最近更新 2026-09-23 18:57:24
分类：开发依赖：代码执行 / 第三方 API应用场景：DevOps / API 集成 / 工作流

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-render
Metadata
name
oo-render
description
Render (render.com). Use this skill for ANY Render request — reading, creating, updating, and deleting data. Whenever a task involves Render, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Render","author":"OOMOL","version":"1.0.5","services":["render"],"icon":"https://static.oomol.com/logo/third-party/render.svg"}

Render

Operate Render through your OOMOL-connected account. This skill calls the render connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Render. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "render" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "render" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • get_current_user — Get the currently authenticated Render user profile.
  • get_service — Get Render service details by service ID.
  • list_deploys — List recent Render deploys for a service.
  • list_services — List Render services with optional workspace, type, and suspension filters.
  • list_workspaces — List Render workspaces available to the authenticated API key.
  • restart_service — Restart a Render service. [write]
  • resume_service — Resume a suspended Render service. [write]
  • rollback_deploy — Trigger a rollback to a previous deploy for a Render service. [destructive]
  • suspend_service — Suspend a Render service. [destructive]
  • trigger_deploy — Trigger a new deploy for a Render service. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Render state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Render is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=render

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources