360 Secure SkillHub
360 安全技能中心

IssueBadge

该 Skill 通过 oo CLI 调用 OOMOL 托管的 IssueBadge 连接器，支持按加密 ID 查询单条发放记录、查询徽章模板列表、分页筛选已发放记录，以及将模板发放给收件人生成公开验证链接；写操作需先与用户确认。凭据由服务端注入，首次使用需安装并登录 oo CLI 或连接 IssueBadge。

oomol
oomol
热度 12.87
最近更新 2026-10-11 08:07:33
分类：自动化依赖：代码执行 / 第三方 API应用场景：工作流 / 模板

安装技能

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

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

IssueBadge

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

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

oo connector run "issue_badge" --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_issued_badge — Retrieve an issued IssueBadge record by encrypted issue ID, including recipient details, metadata, verification URL, and PDF URL.
  • issue_badge — Issue an existing IssueBadge template to a recipient and create a public verification URL. Providing an email address triggers a notification email. Reuse an idempotency key to retrieve the existing issuance without issuing it again. [write]
  • list_badges — List up to 100 badge templates in your IssueBadge organization. The API does not expose pagination for this list.
  • list_issued_badges — List issued IssueBadge records with pagination and optional badge, recipient name, and recipient email filters.

Safety

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

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

Resources