360 Secure SkillHub
360 安全技能中心

Brandfetch

该 Skill 通过 oo CLI 调用 OOMOL 的 Brandfetch 连接器，提供 get_brand 与 get_transaction_info 两个只读动作：按域名、股票代码、ISIN、加密货币符号或品牌 ID 查询品牌档案，或将原始交易标签解析为对应商户品牌档案。凭据由 OOMOL 服务端注入，运行依赖 oo CLI 与已连接的 Brandfetch 账户。

oomol
oomol
热度 55.74
最近更新 2026-09-15 12:59:09
分类：搜索依赖：代码执行 / 第三方 API应用场景：API 集成 / 品牌素材

安装技能

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

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

Brandfetch

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

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

oo connector run "brandfetch" --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_brand — Fetch a Brandfetch brand profile using an explicit domain, ticker, ISIN, crypto symbol, or Brand ID lookup.
  • get_transaction_info — Resolve a raw transaction label into the corresponding Brandfetch merchant brand profile.

Safety

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

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

Resources