360 Secure SkillHub
360 安全技能中心

Mintlify

该 Skill 借助 OOMOL 的 oo CLI 调用 mintlify 连接器，凭据由服务端注入。支持三个动作：查询 Mintlify 部署状态、触发生产部署、按 Git 分支触发预览部署。写入类动作需事先确认，首次使用需安装 oo CLI 并完成登录与连接。

oomol
oomol
热度 37.11
最近更新 2026-09-15 13:25:21
分类：自动化依赖：代码执行 / 第三方 API应用场景：DevOps / 工作流

安装技能

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

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

Mintlify

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

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

oo connector run "mintlify" --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_deployment_status — Get the current status and details of a Mintlify deployment.
  • trigger_deployment — Queue a production deployment for a Mintlify documentation project. [write]
  • trigger_preview_deployment — Create or redeploy a Mintlify preview for a specific Git branch. [write]

Safety

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

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

Resources