yfinance

yfinance global market data interface — retrieve OHLCV, financials, insider transactions, and institutional holdings for US stocks, HK stocks, ETFs, and indices via Yahoo Finance. Free, no API key required.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./a_全网优秀资源/10_大模型/07_skill包/vibe_trading_skills/yfinance/SKILL.md

Quality

Content

65%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 reference with excellent executable examples, but it carries lookup-table padding Claude does not need and lacks any validation/verification guidance for the batch downloads it explicitly recommends. Moving the ticker tables to a reference file and adding a post-download sanity check would lift the weakest dimensions.

Suggestions

Move the Popular Ticker Reference tables into a references/tickers.md file and keep only the conversion rules in SKILL.md, since most ticker-to-company mappings are already known.

Add a validation step for batch downloads, e.g. check that the returned DataFrame is non-empty and retry or back off when Yahoo rate-limits, since the Notes section warns about bans but no code handles them.

Consolidate the indices/ETF/FX examples into a single download call over a list of tickers to avoid repeating the same call signature five times.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight code and tables, but the "Popular Ticker Reference" tables restate knowledge Claude already has (AAPL = Apple, XLK = Technology) and the indices/ETF/FX sections repeat the same yf.download call five times with only the ticker varying, which is more than minor over-explanation yet far from padded prose.	3 / 5
Actionability	Every section contains complete, executable, copy-paste-ready code (yf.download with start/end/interval, ticker.financials, ticker.institutional_holders) plus a concrete config.json example for the project's backtest loader, covering all common cases including batch download and ticker-format conversion.	5 / 5
Workflow Clarity	The sequence is clear (install → ticker conversion → data types → backtest config) and well-structured, but the skill's core operation is batch data retrieval and there is no validation checkpoint (e.g., checking for empty frames or handling Yahoo rate-limit bans after a batch download), which caps workflow clarity at 3 per the batch-operations guideline; it is not 2 because the sequence and step coverage are solid.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested or dead references, but the ~60-line Popular Ticker Reference lookup tables are inline content that belongs in a references/ file, and no bundle files exist to offload detail; this fits "some structure, content that should be separate is inline" rather than the well-split anchor at 4.	3 / 5
	Total	14 / 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, third-person description that clearly conveys what the skill does and its free/no-key nature. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps completeness and weakens discoverability relative to the good-description examples.

Suggestions

Add an explicit trigger clause, e.g. "Use when retrieving market data for US/HK stocks, ETFs, or indices, or when the user mentions Yahoo Finance, stock prices, OHLCV, or ticker data."

Mention remaining capabilities (dividends, splits, FX rates) or collapse to the most important ones so coverage reads as deliberate rather than gapped.

Include a couple of natural synonyms users would say (e.g. "stock quotes", "historical prices") to broaden trigger matching without adding length.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ("retrieve OHLCV, financials, insider transactions, and institutional holdings") with explicit markets and data source, but omits capabilities the body documents (dividends, splits, FX rates), leaving minor gaps that fall short of the comprehensive-coverage anchor.	4 / 5
Completeness	The "what" is clear and specific (data types, markets, source), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; it is not 2 because the "what" is concrete rather than vague.	3 / 5
Trigger Term Quality	Good natural keyword coverage ("OHLCV", "financials", "insider transactions", "US stocks", "HK stocks", "ETFs", "Yahoo Finance"), but common variations like "stock quotes", "historical prices", or "ticker" are missing, so it does not reach the synonym-complete anchor.	4 / 5
Distinctiveness Conflict Risk	Explicitly names the tool, data source (Yahoo Finance), and covered markets, giving distinct triggers with minimal conflict risk; a closely related sibling data-source skill (Tushare for A-shares, per the body's comparison note) creates minor overlap, keeping it below 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: charliedream1/ai_quant_trade
Path: a_全网优秀资源/10_大模型/07_skill包/vibe_trading_skills/yfinance/SKILL.md
Commit: b612402

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.