360 Secure SkillHub
360 安全技能中心

Leiga

该技能通过 oo CLI 调用 leiga connector，对 Leiga 执行读取类操作：按编号或键获取项目、获取项目工单字段 schema、按 issueNo 获取单个工单，以及列出项目与工单。凭据由 OOMOL 服务端注入，用户无需处理令牌；调用前可先查询动作 schema 获取输入输出结构。

oomol
oomol
热度 50.31
最近更新 2026-09-15 13:59:21
分类：协作依赖：代码执行 / 第三方 API应用场景：任务管理 / API 集成

安装技能

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

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

Leiga

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

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

oo connector run "leiga" --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_issue_by_number — Fetch one Leiga issue by its official issueNo identifier.
  • get_issue_schema — Fetch the Leiga issue field schema for one project.
  • get_project — Fetch one Leiga project by its official numeric projectId.
  • get_project_by_key — Fetch one Leiga project by its official project key.
  • list_issues — List Leiga issues for one project using the official issue query body.
  • list_projects — List Leiga projects using the official project list filters.

Safety

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

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

Resources