Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

okx-sentiment-tracker

v1.3.2

Use this skill when the user asks about: 'any crypto news', 'latest news', 'market update', 'daily briefing', 'BTC news', 'ETH news', 'news on SOL', 'search...

0· 142·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for numpy0001/okx-sentiment-tracker.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "okx-sentiment-tracker" (numpy0001/okx-sentiment-tracker) from ClawHub.
Skill page: https://clawhub.ai/numpy0001/okx-sentiment-tracker
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install okx-sentiment-tracker

ClawHub CLI

Package manager switcher

npx clawhub@latest install okx-sentiment-tracker
Security Scan
Capability signals
Crypto
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The stated purpose (OKX news and sentiment) aligns with the commands and workflows in SKILL.md — using an OKX CLI and account credentials is reasonable for this capability. However, the registry metadata lists no required env vars or config paths while SKILL.md explicitly requires API credentials and a ~/.okx/config.toml profile. This metadata/manifest mismatch is inconsistent and may lead to surprise when the skill is run.
!
Instruction Scope
SKILL.md instructs the agent to read/modify CLI config (~/.okx/config.toml), to install and call the `okx` CLI for many read-only commands, and to run broad 'scan all coins' workflows (parallel, batched calls) and fall back to web searches. Two specific issues: (1) it tells the agent to 'always use --profile live' silently (which encourages using live credentials without explicit user confirmation), and (2) it expects reading credentials from the user's config file even though the registry did not declare that path. The broad-then-deep scanning instructions also create a high volume of API calls and access to account-bound API credentials — the scope is large and should be explicitly declared.
Install Mechanism
There is no platform install spec in the registry (skill is instruction-only), but SKILL.md includes an npm install suggestion and a metadata 'install' block pointing to @okx_ai/okx-trade-cli. Installing a public npm CLI is a common delivery method, but because the registry did not expose an install spec, the install will be manual and the package provenance should be verified (npm @okx_ai scope looks plausible but verify package and publisher before running npm -g).
!
Credentials
The skill needs API credentials (AK, SK, passphrase) stored in ~/.okx/config.toml per SKILL.md, yet the registry lists no required env vars or config paths. Requesting live trading/exchange credentials for read-only news endpoints can be reasonable, but the lack of declared required secrets/config paths is an incoherence. Additionally, instructions to silently prefer a 'live' profile increase the risk of accidental use of more privileged keys; users should prefer least-privilege keys scoped only for news/sentiment where possible.
Persistence & Privilege
The skill does not request always:true or any elevated platform privileges. It is instruction-only and does not modify other skills or system-wide settings. Persistence and privilege appear reasonable.
What to consider before installing
Things to check before installing or using this skill: 1) Metadata mismatch: SKILL.md requires API credentials and a ~/.okx/config.toml profile but the registry metadata does not declare these requirements. Expect to supply and store keys manually; the platform will not automatically provide them. 2) Verify the CLI package: SKILL.md recommends installing @okx_ai/okx-trade-cli via npm. Confirm the package identity and publisher on the npm registry (and prefer installing without -g or in a contained environment) before running it. 3) Use least-privilege credentials: Create API keys specifically scoped to read-only/news endpoints if the exchange supports that, and avoid using high-privilege or main account keys. Do not store keys you are not comfortable exposing in ~/.okx/config.toml. 4) Be cautious about 'live' profile behavior: The instructions say to 'always use --profile live' silently. That can cause accidental use of live credentials. Only enable this if you understand and accept that the skill will use your live API profile by default. 5) Volume and privacy: The skill's workflows call many API endpoints in parallel (broad-then-deep scans). Expect significant API usage and aggregated output. If you have concerns about data leaving your environment, review what the OKX CLI transmits and whether any results are sent externally by the agent. 6) If you want to proceed safely: run the OKX CLI in a restricted or sandboxed environment, inspect and test the npm package locally, and supply a dedicated, read-only 'news/sentiment' API profile rather than your main trading keys. Reason for 'suspicious': the skill appears functionally coherent for its stated purpose, but the manifest/metadata inconsistencies and the silent 'use live profile' instruction are material concerns that warrant manual review before use.

Like a lobster shell, security has layers — review code before you run it.

latestvk977trh74ffcsrhhfs59cfe56185m23v
142downloads
0stars
2versions
Updated 1d ago
v1.3.2
MIT-0

OKX News & Sentiment

Crypto news aggregation and coin sentiment analysis for OKX. All commands are read-only and require API credentials (OAuth2.1).

Capabilities

User IntentCommand
Latest/important newsokx news latest
Coin-specific newsokx news by-coin
Keyword news searchokx news search
Sentiment-filtered newsokx news by-sentiment
Full article contentokx news detail
Coin sentiment snapshotokx news coin-sentiment
Sentiment trendokx news coin-trend
Sentiment rankingokx news sentiment-rank
News source listokx news platforms

Prerequisites

  1. Install okx CLI:
    npm install -g @okx_ai/okx-trade-cli
    
  2. Configure credentials in ~/.okx/config.toml
  3. Verify setup:
    okx news latest --limit 3
    

OKX News does not support demo mode. Always use --profile live silently — don't mention it unless there's an error.

On "not available in demo" errors: the user's current profile is configured with demo/simulated credentials. Tell the user: "News module does not support demo mode. Please switch to a live profile." Guide them to either:

  • Use --profile live if a live profile exists: okx --profile live news latest
  • Or create one: okx config add-profile AK=<key> SK=<secret> PP=<passphrase> name=live

All commands support --json for raw JSON output.

Quickstart

# Latest news
okx news latest --limit 5

# Today's important news
okx news important --begin $(date -d 'today 00:00:00' +%s000 2>/dev/null || date -v0H -v0M -v0S +%s000)

# BTC news
okx news by-coin --coins BTC

# Search for SEC ETF news
okx news search --keyword "SEC ETF"

# BTC sentiment overview
okx news coin-sentiment --coins BTC

# Trending coins (hottest right now)
okx news sentiment-rank

Intent → Command Mapping

Browse News

latest, by-coin, and search default --importance low, which returns all news (both high and low importance). Pass --importance high only when the user explicitly asks for major / breaking / important news. The dedicated okx news important command is a shortcut for that case.

User saysCommand
"what's been happening in crypto lately" / "catch me up on recent news"okx news latest
"any big news today" / "what are the major stories right now"okx news important
"what happened in crypto yesterday"okx news latest --begin <yesterday_0am> --end <today_0am>
"any news on BTC recently" / "what's going on with BTC"okx news by-coin --coins BTC
"any major updates on ETH or SOL"okx news by-coin --coins ETH,SOL --importance high

Search News

User saysCommand
"any updates on the SEC ETF decision"okx news search --keyword "SEC ETF"
"what's the latest on stablecoin regulation"okx news search --keyword "stablecoin regulation"
"any news about the Bitcoin halving"okx news search --keyword "Bitcoin halving"

Coin Sentiment Analysis

User saysCommand
"is the market bullish or bearish on BTC right now" / "how do people feel about BTC"okx news coin-sentiment --coins BTC
"compare how people feel about ETH vs SOL"okx news coin-sentiment --coins ETH,SOL
"how has BTC sentiment changed over the past 24 hours"okx news coin-trend BTC --period 1h --points 24
"show me BTC sentiment over the past week"okx news coin-trend BTC --period 24h --points 7
"what's hot in crypto right now" / "which coins are getting the most attention"okx news sentiment-rank
"which coins are people most excited about" / "top bullish coins"okx news sentiment-rank --sort-by bullish
"which coins have the most negative sentiment"okx news sentiment-rank --sort-by bearish

Sentiment Anomaly Detection (multi-coin)

User saysWorkflow
"哪些币种情绪变化最大" / "any sentiment anomalies" / "which coins flipped sentiment"Anomaly Detection workflow
"过去一周有什么异动" / "sudden sentiment shifts" / "sentiment reversal"Anomaly Detection workflow
"有没有突然转看涨/看跌的" / "any coins turning bullish/bearish"Anomaly Detection workflow

These queries require a broad-then-deep approach: first scan all coins for anomalies, then deep-dive with news correlation. Follow the multi-phase workflow in references/workflows.md — do NOT just pick a few coins to analyze.

Source-Filtered News

Use --platform to filter by news source directly. Always resolve the exact value from okx news platforms — do not guess platform identifiers from the user's wording.

User saysCommand
"ChainCatcher 最近报道了什么" / "show me news from ChainCatcher"okx news latest --platform <platform_id> --limit 10
"Odaily 有什么新闻" / "news from TechFlowPost"okx news latest --platform <platform_id> --limit 10
"吴说区块链最近有什么" / "news from a specific outlet"okx news latest --platform <platform_id> --limit 20

Important: When filtering by source, use a larger --limit (10–20) to maximize results, since individual sources typically have fewer articles than the aggregated feed. --importance low (the default) is the right setting here; do not narrow to --importance high.

Posting cadence is uneven across platforms. The API defaults --begin to 72 hours ago, which is too narrow for bursty sources and will often return 0 results. If a --platform-filtered query returns fewer than ~5 items (or 0), retry with --begin set to 7 days back, then 30 days back before concluding the source has no data. Resolve candidate platform IDs from okx news platforms; do not hardcode assumptions about which platforms are active.

Cross-Skill Workflows

See references/workflows.md for multi-step scenarios (market overview, daily briefing, etc.) and full MCP tool → CLI mapping.

Command Reference

okx news latest

Get the latest crypto news sorted by time.

okx news latest [--coins BTC,ETH] [--begin <ms>] [--end <ms>]
               [--importance high|low] [--platform <source>]
               [--detail-lvl brief|summary|full] [--lang zh-CN|en-US]
               [--limit 10] [--after <cursor>] [--json]

--importance default is low (returns all news, both high and low). Pass --importance high to narrow to breaking / major news only — or use okx news important.


okx news important

Get high-impact breaking news (reported by multiple sources).

okx news important [--coins BTC,ETH] [--begin <ms>] [--end <ms>]
                  [--detail-lvl brief|summary|full]
                  [--lang zh-CN|en-US] [--limit 10] [--json]

okx news by-coin

Get news for specific coins.

okx news by-coin --coins <BTC,ETH,...>
               [--importance high|low] [--platform <source>]
               [--begin <ms>] [--end <ms>] [--lang zh-CN|en-US]
               [--limit 10] [--json]

--importance default is low (returns all news). Pass --importance high only for breaking / major news.


okx news search

Full-text keyword search with optional filters.

okx news search --keyword <text>
               [--coins BTC,ETH] [--importance high|low]
               [--platform <source>]
               [--sentiment bullish|bearish|neutral]
               [--sort-by latest|relevant]
               [--begin <ms>] [--end <ms>] [--lang zh-CN|en-US]
               [--limit 10] [--after <cursor>] [--json]

--importance default is low (returns all news). Pass --importance high only for breaking / major news.


okx news detail

Get full article content by ID.

okx news detail <id>                  # news ID from previous result
               [--lang zh-CN|en-US] [--json]

okx news by-sentiment

Browse news filtered by sentiment (no keyword needed).

okx news by-sentiment --sentiment <bullish|bearish|neutral>
               [--coins BTC,ETH] [--importance high|low]
               [--sort-by latest|relevant]
               [--begin <ms>] [--end <ms>] [--lang zh-CN|en-US]
               [--limit 10] [--after <cursor>] [--json]

--importance default is low (returns all news). Pass --importance high only for breaking / major news.


okx news platforms

List available news platforms. Use the returned values with --platform on latest, by-coin, or search commands to filter by source.

okx news platforms [--json]

okx news coin-sentiment

Get current sentiment snapshot for specific coins.

okx news coin-sentiment --coins <BTC,ETH,...>
               [--period 1h|4h|24h]  # aggregation granularity, default 24h
               [--json]

Returns: symbol, label (bullish/bearish/neutral/mixed), bullishRatio, bearishRatio, mentionCount.


okx news coin-trend

Get time-series sentiment trend for a coin. Note: uses positional arg (not --coins).

okx news coin-trend <coin>            # positional arg, e.g. BTC
               [--period 1h|4h|24h]  # aggregation granularity, default 1h
               [--points 24]          # trend data points, default 24
               [--json]

trendPoints guide: 1h period → use 24 (last 24h), 4h → use 6, 24h → use 7.


okx news sentiment-rank

Get coin ranking by social hotness or sentiment direction.

okx news sentiment-rank [--period 1h|4h|24h]
               [--sort-by hot|bullish|bearish]  # hot=by mentions (default), bullish, bearish
               [--limit 10]                     # max 50
               [--json]

MCP Tool Reference

ToolDescription
news_get_latestLatest news sorted by time. Server default importance=high (narrow); pass importance=low to broaden to all news.
news_get_by_coinNews for specific coins (coins is comma-separated string)
news_searchFull-text keyword search with filters (optional sentiment filter)
news_get_detailFull article content by ID
news_get_domainsList available news source domains
news_get_coin_sentimentSentiment snapshot (no trendPoints) or time-series trend (pass trendPoints)
news_get_sentiment_rankingCoin ranking by hotness or sentiment direction

Coin Symbol Normalization

The API only accepts standard uppercase ticker symbols (e.g. BTC, ETH, SOL). Users may refer to coins by full names, abbreviations, slang, or local-language nicknames. Always resolve these to the correct ticker before passing to any command. If the intended coin is ambiguous, ask the user to confirm before querying.

Empty Results & Web Search Fallback

OKX news data may be sparse for niche coins or highly specific keyword searches. The API default --begin window is only 72 hours, which alone accounts for many empty results. When a command returns empty or insufficient results, apply these steps in order — do not skip to web search:

  1. If --platform was used — broaden --begin to 7 days back, then 30 days back, before changing anything else. Bursty sources routinely return 0 items in the default window but dozens over a wider range.
  2. If --importance high was passed — drop it (default is already low = all news).
  3. Broaden --begin / --end for any query (not just --platform) when a narrow time window is suspected.
  4. Drop --coins to get general news if the coin-specific query yielded nothing.
  5. Use web search as a supplement — search the web for "<topic> news site:coindesk.com OR site:cointelegraph.com OR site:theblock.co" to gather additional context, then combine with any OKX results into a unified briefing.
  6. Be transparent — tell the user which results came from OKX API vs. web search so they can judge source credibility.

This fallback is especially valuable for:

  • Coins with low coverage (e.g. newly listed tokens)
  • Highly specific keyword searches with no matches
  • --platform queries where the chosen source has uneven posting cadence

Known Limitations

Source Coverage

Platform posting cadence varies and changes over time. Some sources publish many articles per day; others post in bursts with quiet stretches in between. A source returning few or zero articles in the default 72-hour window is not evidence that it is inactive — it may simply not have posted recently, or its recent posts may have been deduplicated out.

Before concluding a --platform-filtered query has no data:

  1. Broaden --begin to 7 days back, then 30 days back, and retry.
  2. If still empty after a 30-day window, report to the user that no recent articles were found for that source and suggest either removing --platform (to fall back to the aggregated feed) or web search.

Do not hardcode assumptions about which platforms are active — resolve candidates from okx news platforms and let the data speak.

Historical Search Limitations

okx news search and okx news by-coin primarily index recent articles (typically today and recent days). Searching with --begin/--end for dates more than ~7 days ago may return empty results even if articles existed at that time. This is an API indexing limitation, not a data absence.

For historical analysis, okx news coin-trend (sentiment trend data) is more reliable than article search — it retains time-series data for longer periods.

Edge Cases

  • Pagination: use --after <cursor> to get next page; cursor comes from nextCursor in response
  • Time parameters: --begin / --end are Unix epoch milliseconds
  • Coins format: comma-separated uppercase symbols, e.g. BTC,ETH,SOL — never pass full names or aliases
  • coin-trend --points: always pass explicitly; 1h→24, 4h→6, 24h→7
  • Language: inferred from user's message — --lang zh-CN for Chinese, --lang en-US for English (default)
  • sentiment-rank --sort-by: hot=by mention count (default), bullish=most bullish, bearish=most bearish

Comments

Loading comments...