360 Secure SkillHub
360 安全技能中心

Ashby

该 Skill 通过 oo CLI 调用 OOMOL 托管的 Ashby 连接器，提供 API key 信息、候选人列表、职位列表和候选人搜索四类只读动作。运行前用 oo connector schema 查看输入输出约定，再用 oo connector run 提交 JSON 载荷并获取结构化响应。凭据由服务端注入，安装、登录、连接与计费问题按需按文档步骤处理。

oomol
oomol
热度 36.19
最近更新 2026-09-15 12:19:06
分类：搜索依赖：代码执行 / 第三方 API应用场景：研究

安装技能

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

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

Ashby

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

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

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

  • api_key_info — Retrieve information about the Ashby API key used for this connection.
  • list_candidates — List Ashby candidates with optional pagination and incremental sync filters.
  • list_jobs — List Ashby jobs with optional status, timestamp, expansion, pagination, and sync filters.
  • search_candidates — Search Ashby candidates by email and/or name for small result sets such as autocomplete.

Safety

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

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

Resources