360 Secure SkillHub
360 安全技能中心

incident.io

该 Skill 通过 OOMOL 的 oo CLI 调用 incident_io 连接器，按指定 action 查询 incident.io 数据，包括单个事件与动作详情，以及事件列表、跟进动作列表、事件状态和严重级别；凭据由 OOMOL 服务端注入，列出的动作均为读取类，运行前先用 schema 命令获取输入字段。

oomol
oomol
热度 34.04
最近更新 2026-09-15 12:10:22
分类：协作依赖：代码执行 / 第三方 API应用场景：任务管理 / 工作流

安装技能

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

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

incident.io

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

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

oo connector run "incident_io" --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_action — Get a single incident.io action by ID.
  • get_incident — Get a single incident.io incident by full ID or numeric reference.
  • list_actions — List incident.io actions with optional incident and mode filters.
  • list_incident_statuses — List incident.io incident statuses configured for the organization.
  • list_incidents — List incident.io incidents with optional stable filters and pagination.
  • list_severities — List incident.io severities configured for the organization.

Safety

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

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

Resources