360 Secure SkillHub
360 安全技能中心

Workpath

该 Skill 借助 OOMOL 的 oo CLI，通过 workpath 连接器查询 Workpath 中的目标、关键结果、团队与用户信息，提供 get/list 等只读动作；凭据由平台服务端注入，首次使用需完成 CLI 登录与 Workpath 连接授权。

oomol
oomol
热度 23.38
最近更新 2026-09-15 12:55:43
分类：搜索依赖：代码执行 / 第三方 API应用场景：API 集成

安装技能

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

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

Workpath

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

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

oo connector run "workpath" --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_goal — Get one Workpath goal by its unique identifier.
  • get_goal_key_result — Get one Workpath key result by its unique identifier using the official convenience endpoint.
  • get_team — Get one Workpath team by its unique identifier.
  • get_user — Get one Workpath user by their unique identifier.
  • list_goal_key_results — List all key results associated with a specific Workpath goal.
  • list_goals — List Workpath goals visible to the API client, optionally filtered by an overlapping date range.
  • list_teams — List Workpath teams visible to the API client.
  • list_users — List Workpath users visible to the API client.

Safety

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

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

Resources