360 Secure SkillHub
360 安全技能中心

Templated

该 Skill 通过 OOMOL 的 oo CLI 调用 templated 连接器，支持查询账户、模板与渲染，并可创建渲染（输出图片或 PDF）及删除渲染记录；凭据由服务端注入，执行前需先查看动作 schema，写入与删除操作需先与用户确认。

oomol
oomol
热度 51.15
最近更新 2026-09-15 13:52:25
分类：创作依赖：代码执行 / 第三方 API应用场景：图像生成

安装技能

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

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

Templated

Operate Templated through your OOMOL-connected account. This skill calls the templated 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 Templated. 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 "templated" --action "<action_name>"

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

oo connector run "templated" --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

  • create_render — Create a Templated render from one template with optional shared layer overrides and image or PDF output settings. [write]
  • delete_render — Delete a Templated render by its render ID. [destructive]
  • get_account — Get the current Templated account associated with the API key.
  • get_render — Retrieve a single Templated render by its render ID.
  • get_template — Retrieve a single Templated template by its template ID.
  • list_renders — List all renders owned by the current Templated account.
  • list_templates — List Templated templates with optional filters for name, dimensions, and tags.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Templated 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 — Templated 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=templated

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

Resources