CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured, highly actionable data-source skill with clear interface routing and clean progressive disclosure through six one-level-deep references. The only meaningful weakness is duplication between Quick Start and the Historical OHLCV section.

Suggestions

De-duplicate the Quick Start and §1 Historical OHLCV sections — keep one canonical get_market_data + loader example and cross-reference it instead of repeating both blocks.

Trim the opening "yfinance is an open-source Python wrapper…" sentence, which restates a concept Claude already knows, to tighten conciseness toward 3.

DimensionReasoningScore

Conciseness

Mostly efficient with lean code blocks, but the Quick Start and §1 Historical OHLCV duplicate the same get_market_data JSON and DataLoader snippet, and the opening line restates what yfinance is; tightening the redundancy would reach 3.

2 / 3

Actionability

Throughout the body are complete, copy-paste-ready executable snippets (loader calls, yf.Ticker usage, ticker-conversion rules, config.json examples) with concrete parameters rather than pseudocode.

3 / 3

Workflow Clarity

A clear decision path is laid out — prefer get_market_data for OHLCV, fall back to the DataLoader for scripts, use raw yfinance only for non-OHLCV data — and the reference table maps each interface to its use; the skill is read-only so no destructive-validation checkpoint is required.

3 / 3

Progressive Disclosure

The body is a concise overview that points to six one-level-deep reference docs via a well-signaled table using the skill-name prefix, with an explicit path-convention note — easy navigation, no deep nesting.

3 / 3

Total

11

/

12

Passed

Description

82%

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 with strong natural trigger terms and low conflict risk, weakened only by the absence of an explicit "Use when…" trigger clause. Adding when-to-use guidance would lift completeness from 2 to 3.

Suggestions

Append an explicit trigger clause, e.g. "Use when retrieving Yahoo Finance market data — historical OHLCV, financials, insider transactions, or institutional holdings for US/HK stocks, ETFs, or indices."

Add common natural variations users say ("stock prices", "historical prices", "quotes") alongside OHLCV to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "retrieve OHLCV, financials, insider transactions, and institutional holdings" — across named markets (US stocks, HK stocks, ETFs, indices), matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers what the skill does, but there is no "Use when…" clause or equivalent explicit trigger guidance; "Free, no API key required" is a property, not a trigger, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Uses natural terms a user would say when needing this skill — "Yahoo Finance", "financials", "insider transactions", "institutional holdings", "ETFs", "indices" — giving good coverage rather than just one generic keyword.

3 / 3

Distinctiveness Conflict Risk

The Yahoo Finance source plus specific global-market data types (insider transactions, institutional holdings, OHLCV) carve a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 6 missing, 6 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
HKUDS/Vibe-Trading
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.