360 Secure SkillHub
360 安全技能中心

Indeed

该 Skill 通过 OOMOL 的 oo CLI 调用 indeed 连接器：查看当前用户与关联雇主、按 IRI 获取单个或多个雇主职位、按条件列出雇主职位，以及更新或清除 sourced 职位发布的更新。凭据由 OOMOL 服务端注入。使用前需安装并登录 oo CLI 并连接 Indeed；write 与 destructive 操作需先向用户确认。

oomol
oomol
热度 22.11
最近更新 2026-09-15 12:21:47
分类：自动化依赖：代码执行 / 第三方 API / 读写文件应用场景：工作流 / 数据处理

安装技能

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

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

Indeed

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

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

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

  • clear_sourced_job_posting_updates — Clear updates previously applied to one sourced Indeed job posting. [destructive]
  • find_employer_jobs — List jobs for the employer represented by the OAuth token, with filters and cursor pagination.
  • get_current_user — Get the Indeed user and associated employers represented by the OAuth access token.
  • get_job — Get one Indeed employer job by its EmployerJob IRI.
  • get_jobs — Get multiple Indeed employer jobs by their EmployerJob IRIs.
  • update_sourced_job_postings — Update supported fields on one sourced Indeed job posting. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Indeed 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 — Indeed is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:

    https://console.oomol.com/app-connections?provider=indeed

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

Resources