360 Secure SkillHub
360 安全技能中心

OpenAlex

该 Skill 通过 oo CLI 调用 OpenAlex 连接器，提供自动补全、实体与作品获取、列表检索、过滤、分页和分组等只读操作；调用时需按 action 的实时 Schema 构造 JSON 负载，凭据由 OOMOL 服务端注入。

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

安装技能

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

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

OpenAlex

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

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

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

  • autocomplete — Return OpenAlex autocomplete suggestions for a search string.
  • get_entity — Get one OpenAlex entity by identifier from a supported collection.
  • get_work — Get one OpenAlex work by identifier.
  • list_entities — List, search, filter, page, or group OpenAlex entities from the supported collections.
  • list_works — List, search, filter, page, or group OpenAlex works with work-focused normalized fields.

Safety

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

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

Resources