360 Secure SkillHub
360 安全技能中心

Venafi TLS Protect Cloud

该 Skill 通过 OOMOL oo CLI 调用 Venafi TLS Protect Cloud 连接器，提供获取证书、获取证书请求和列出证书三个只读操作；使用前需已安装并登录 oo CLI，并在 OOMOL 中连接 Venafi TLS Protect Cloud。

oomol
oomol
热度 22.94
最近更新 2026-09-15 13:29:45
分类：安全依赖：代码执行 / 第三方 API应用场景：DevOps / API 集成

安装技能

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

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

Venafi TLS Protect Cloud

Operate Venafi TLS Protect Cloud through your OOMOL-connected account. This skill calls the venafitlsprotectcloud 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 Venafi TLS Protect Cloud. 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 "venafitlsprotectcloud" --action "<action_name>"

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

oo connector run "venafitlsprotectcloud" --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_certificate — Retrieve a certificate by its Venafi TLS Protect Cloud identifier.
  • get_certificate_request — Retrieve a certificate request by its Venafi TLS Protect Cloud identifier.
  • list_certificates — List certificates visible to the Venafi TLS Protect Cloud account.

Safety

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

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

Resources