SKILLEMALL.ai

AB tvfetch

Fetch TradingView market data — historical OHLCV bars, live price streams, symbol search, technical indicators, and statistical analysis for any symbol (stocks, crypto, forex, futures, indices, commodities). No API key required. Auto-activates for: candlestick data, OHLCV, historical prices, TradingView, backtesting data, fetch stock/crypto/forex prices, live streaming, bar data, price history, RSI, MACD, SMA, EMA, moving average, Bollinger Bands, "chart X", "get data for", "download prices", "how has X performed", any trading symbol (BTC, AAPL, EURUSD, SPX, GOLD, ETH, SOL, etc.)

ClawHub Agent Skills author: Tarun Khatri v1.0.0 MIT-0 53 files · 2 scripts body ≈ 3 499 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process B 71/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

IntegrationInfrastructureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
B
71/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 49. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 71/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 83 steps
  • 100Failures and branches. 7 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3499 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • -33 of 3 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +3Description length 586: enough signal without eating the budget
  • +4Structure: 38 headings
  • +3Step-by-step instructions: 83 items
  • +3Output format is stated explicitly
  • +4Has examples (15 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.

External checks

ClawHub: suspicious
TVFetch is a coherent market-data skill, but it asks users to extract and persist sensitive TradingView session tokens with under-disclosed handling risks.
LLM: suspicious (high) · VirusTotal: · 29 May 2026