CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

yfinance

yfinance global market data interface — retrieve OHLCV and research data for US, HK, and Canadian stocks, ETFs, and indices via Yahoo Finance. Free, no API key required.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/yfinance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill body: executable examples for every data type, a clear interface-selection order, and exemplary progressive disclosure through a table of real, selectively-loaded reference docs. The main improvements are trimming the authoring meta blockquote, deduplicating the OHLCV quick-start patterns, and adding brief error-recovery guidance for rate limits.

DimensionReasoningScore

Conciseness

The body is dense with tables and executable code and assumes Claude's competence (no library tutorials, no concept explanations). Not 5 because the 'Path convention' blockquote is skill-authoring meta-commentary irrelevant to using the skill, and the Quick Start and Historical OHLCV sections repeat the same tool-call and loader patterns.

4 / 5

Actionability

Copy-paste-ready JSON tool calls and Python snippets throughout, a concrete ticker conversion table with explicit rules, seven data types each with a complete working example, and backtest config.json examples. The common cases are fully covered with executable guidance.

5 / 5

Workflow Clarity

The interface decision tree is unambiguous — prefer get_market_data, fall back to the DataLoader, use bounded yahoo_ticker/yahoo_download for extra fields, consult the per-interface reference docs — and the auto-routing rules are spelled out. Not 5 because there are no explicit error-recovery checkpoints (e.g., what to do when a Yahoo rate-limit ban or empty response occurs beyond a one-line preventative note).

4 / 5

Progressive Disclosure

All six referenced files exist in references/, are one level deep, and are surfaced through a table that states what each covers, with the explicit instruction to 'read the one you need rather than loading them all'. The body itself stays a concise overview with quick-start content — exactly the well-signaled one-level structure the top anchor describes.

5 / 5

Total

18

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that clearly states what the skill does and its free/no-key access model, but it omits any explicit 'when to use' trigger guidance, which caps completeness. Keyword coverage is good though missing a few natural synonyms like 'historical prices' or 'quotes'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when fetching historical prices, quotes, or fundamentals for US, HK, or Canadian tickers via Yahoo Finance.'

Include natural synonyms users would say — 'historical prices', 'stock quotes', 'ticker data' — alongside 'OHLCV and research data'.

Briefly enumerate what 'research data' covers (e.g., financial statements, holdings, dividends) to sharpen the capability list.

DimensionReasoningScore

Specificity

Names the concrete action ('retrieve OHLCV and research data') with enumerated scope ('US, HK, and Canadian stocks, ETFs, and indices via Yahoo Finance'), plus the access model ('Free, no API key required'). Not 5 because 'research data' is a bundled, vague term rather than multiple individually named actions.

4 / 5

Completeness

The 'what' is clear (retrieve OHLCV and research data for specified markets via Yahoo Finance), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is entirely absent, which caps this at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage — 'yfinance', 'Yahoo Finance', 'market data', 'OHLCV', 'stocks', 'ETFs', 'indices' are all phrases a user would say. Not 5 because common variations like 'historical prices', 'quotes', 'ticker data', or 'financial data' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche: Yahoo Finance-sourced global market data scoped to US, HK, and Canadian instruments, unlikely to trigger for unrelated skills. Not 5 because it could overlap with other market-data source skills (e.g., a China/A-share data skill) where the market split is the only differentiator.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

HKUDS/Vibe-Trading

Path

agent/src/skills/yfinance/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.