360 Secure SkillHub
360 安全技能中心

SignPath

该 Skill 通过 oo CLI 调用 OOMOL 的 signpath 连接器操作 SignPath：提交哈希签名请求并返回签名结果、查询签名请求状态与元数据以轮询完成情况、列出可见签名策略（可按项目与策略 slug 过滤）。运行前用 schema 命令获取动作的输入输出定义；标记 [write] 的动作会改变 SignPath 状态，需用户确认后执行。凭证由 OOMOL 服务端注入。

oomol
oomol
热度 53.52
最近更新 2026-09-20 11:39:05
分类：自动化依赖：代码执行 / 第三方 API应用场景：DevOps / 工作流 / API 集成

安装技能

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

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

SignPath

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

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

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

  • fast_sign_hash — Submit a fast SignPath hash-signing request using the REST API payload.json contract and return the signature result immediately. [write]
  • get_signing_request — Get the current status and metadata for a SignPath signing request so callers can poll for completion.
  • list_signing_policies — List SignPath signing policies visible to the API token, optionally filtered by project and policy slug.

Safety

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

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

Resources