360 Secure SkillHub
360 安全技能中心

Tuskr

该 Skill 通过 oo CLI 调用 OOMOL 托管的 Tuskr 连接器，凭据由服务端注入。支持列出项目、测试用例与测试运行，以及创建项目、测试用例、测试运行和批量写入测试运行结果；写入类动作需先与用户确认。使用前需已安装 oo CLI 并完成登录与 Tuskr 连接。

oomol
oomol
热度 23.37
最近更新 2026-09-15 12:55:11
分类：开发依赖：代码执行 / 第三方 API应用场景：任务管理 / API 集成 / 数据处理

安装技能

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

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

Tuskr

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

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

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

  • add_test_run_results — Add the same Tuskr result to multiple test cases in a test run. [write]
  • create_project — Create a Tuskr project. [write]
  • create_test_case — Create a Tuskr test case in a project suite section. [write]
  • create_test_run — Create a Tuskr test run. [write]
  • list_projects — List Tuskr projects with optional filters.
  • list_test_cases — List Tuskr test cases for a project.
  • list_test_runs — List Tuskr test runs for a project.

Safety

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

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

Resources