360 Secure SkillHub
360 安全技能中心

Token Metrics

该 Skill 通过 OOMOL 的 oo CLI 调用 token_metrics 连接器，提供六个只读动作：查询代币价格、日线与小时线 OHLCV、代币列表、市值排名和交易信号。运行时先查看动作 schema，再以 JSON 载荷执行；凭证由 OOMOL 服务端注入，命令失败时才按提示安装 CLI、登录并连接服务。

oomol
oomol
热度 34.38
最近更新 2026-09-15 12:55:07
分类：数据依赖：代码执行 / 第三方 API应用场景：市场分析 / 财务 / API 集成 / 数据处理

安装技能

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

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

Token Metrics

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

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

oo connector run "token_metrics" --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_prices — Retrieve current Token Metrics price records for selected cryptocurrencies.
  • list_daily_ohlcv — List daily open, high, low, close, and volume records from Token Metrics.
  • list_hourly_ohlcv — List hourly open, high, low, close, and volume records from Token Metrics.
  • list_tokens — List Token Metrics tokens and retrieve identifiers used by other market-data actions.
  • list_top_market_cap_tokens — List cryptocurrencies ranked by market capitalization in Token Metrics.
  • list_trading_signals — List Token Metrics long, short, or neutral trading signals with optional filters.

Safety

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

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

Resources