CtrlK
BlogDocsLog inGet started
Tessl Logo

yahoo-finance

Financial data from Yahoo Finance: stock/bond prices, credit analysis, macro dashboard, FX rates, ETF flows, fundamentals, and news. Use when the user asks about stock prices, bond yields, credit metrics, leverage ratios, debt/ebitda, interest coverage, macro indicators (VIX, DXY, treasury yields, oil, gold, BTC), LatAm FX (ARS, BRL, CLP, MXN, COP), ETF holdings, income statements, balance sheets, cash flow, financial news, options chains, dividend history, or analyst ratings/upgrades. Commands: yf price, yf quote, yf compare, yf credit, yf macro, yf fx, yf flows, yf history, yf fundamentals, yf news, yf search, yf options, yf dividends, yf ratings.

95

3.28x
Quality

96%

Does it follow best practices?

Impact

92%

3.28x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

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

This is an excellent skill description that thoroughly covers what the skill does, when to use it, and includes rich trigger terms spanning multiple financial domains. The explicit 'Use when...' clause with comprehensive keyword coverage ensures reliable skill selection, and the enumerated commands provide additional clarity. The description is information-dense without being padded with fluff.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: stock/bond prices, credit analysis, macro dashboard, FX rates, ETF flows, fundamentals, news, options chains, dividend history, analyst ratings. Also enumerates specific commands (yf price, yf quote, etc.).

3 / 3

Completeness

Clearly answers both 'what' (financial data from Yahoo Finance covering stocks, bonds, credit, macro, FX, ETFs, fundamentals, news) and 'when' with an explicit 'Use when the user asks about...' clause listing comprehensive trigger scenarios.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'stock prices', 'bond yields', 'credit metrics', 'leverage ratios', 'debt/ebitda', 'interest coverage', 'VIX', 'DXY', 'treasury yields', specific currency codes (ARS, BRL, etc.), 'income statements', 'balance sheets', 'cash flow', 'options chains', 'dividend history', 'analyst ratings/upgrades'.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to Yahoo Finance financial data with specific command names (yf price, yf macro, etc.) and a well-defined niche. The Yahoo Finance branding and specific command syntax make it highly distinguishable from generic financial or data analysis skills.

3 / 3

Total

12

/

12

Passed

Implementation

92%

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

This is a strong, well-structured skill that efficiently documents a CLI tool with concrete examples for every command. The command table format is excellent for quick reference, and the workflow guidance section adds real value for routing decisions. Minor improvement could come from linking to detailed documentation for complex commands like credit analysis.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It uses a table format for commands which is highly token-efficient, avoids explaining what Yahoo Finance is or how CLI tools work, and every section earns its place. The 'When to Use Which Command' section adds genuine value for routing decisions.

3 / 3

Actionability

Every command has a concrete, copy-paste-ready example in the table. The setup is a single executable command. The workflow suggestions ('Morning check', 'Deep dive equity') provide specific command sequences. The --json flag is clearly documented.

3 / 3

Workflow Clarity

The 'When to Use Which Command' section provides clear workflow sequences (e.g., 'yf quote → yf fundamentals → yf history' for deep dives). This is primarily a read-only data retrieval tool with no destructive operations, so validation checkpoints aren't needed. The single-step commands are unambiguous.

3 / 3

Progressive Disclosure

The content is well-organized with clear sections (Setup, Commands table, When to Use, Error Handling, Output), but everything is inline in one file. The commands table could potentially link to more detailed documentation for complex commands like 'credit' or 'fundamentals', and there's no reference to the actual script source or additional docs.

2 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

10

/

11

Passed

Repository
NeverSight/skills_feed
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.