360 Secure SkillHub
360 安全技能中心

Valyu

该 Skill 通过 OOMOL 的 oo CLI，以 oo connector schema 和 oo connector run 调用 valyu 连接器的 search 动作：先用 JSON 载荷传入参数，再返回结构化结果与执行 ID。凭据由 OOMOL 服务端注入，仅在命令报错时按提示安装 CLI 或连接账户；仅含检索动作，不含其他 Valyu 操作。

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

安装技能

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

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

Valyu

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

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

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

  • search — Search web, academic, financial, and proprietary data sources with Valyu.

Safety

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

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

Resources