CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

yahoo-finance

Retrieve public Yahoo Finance market, company, financial, ownership, and analyst data through authorized access.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/yahoo-finance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The body is an exemplary lean overview: tightly organized sections, a clear five-step workflow with completion gates, and honest boundaries, with no wasted tokens. Its main weakness is actionability — it never shows how to actually reach Yahoo Finance data (no URL patterns, endpoints, or examples), leaving execution details entirely to inference.

Suggestions

Add concrete fetch specifics, e.g. example URLs or query patterns (such as finance.yahoo.com/quote/{ticker} for quotes and key statistics), so the routing guidance is executable rather than directional.

Strengthen the completion gates with a brief how-to for each check (e.g. how to detect delayed vs real-time data on a page), or add a short worked example of a request-and-cited-answer cycle.

Clarify in the tool routing table when `render_chart` applies versus simply reporting numbers, since the current entry ("Present verified price or metric trends") leaves the trigger conditions implicit.

DimensionReasoningScore

Conciseness

The ~32-line body is lean and assumes Claude's competence: no explanations of known concepts, no padding, every section (tool routing, workflow, gates, boundaries, delivery) carries operational weight. Only the one-line copyright notice is non-instructional, which does not reach the level of trimmable over-explanation at score 4.

5 / 5

Actionability

The tool routing table ("web_fetch ... Fetch authorized public Yahoo Finance pages when text extraction is available") and parameter checklist ("Confirm ticker, exchange, instrument type, currency, and timezone") give some concrete guidance, but there are no URL patterns, endpoints, commands, or worked examples — how to actually fetch and parse the data is left unstated. This fits "some concrete guidance but incomplete; missing key details" rather than the mostly-executable level of score 4.

3 / 5

Workflow Clarity

Five clearly sequenced workflow steps plus a "Completion gates" checklist ("Check delayed versus real-time status", "Verify corporate actions and fiscal periods") and a failure path ("report when access is unavailable") provide most checkpoints. It falls short of score 5 because there is no explicit validate-and-recover feedback loop and the gates state what to verify without how.

4 / 5

Progressive Disclosure

This is a single-file skill under 50 lines with no references/, scripts/, or assets/ directories and no external content that needs splitting; its well-organized, clearly headed sections meet the rubric's simple-skill standard for a top score. Nothing is inlined that belongs in a separate file and no references are dangling.

5 / 5

Total

17

/

20

Passed

Description

65%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.

The description is specific, third-person, and cleanly scoped to a named data source with minimal conflict risk, but it omits any "Use when..." trigger guidance and relies on a single generic verb ("retrieve"), capping completeness and specificity. Adding an explicit when-to-use clause and common user terms (stock, ticker, quote, earnings) would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for stock quotes, ticker data, company financials, analyst ratings, or any Yahoo Finance data."

Replace or supplement the single verb "Retrieve" with more distinct concrete actions (e.g. "Fetch current and historical prices, pull company profiles and financial statements, look up analyst ratings and ownership").

Include natural synonyms users actually say — "stock", "ticker", "quote", "price", "earnings" — to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Retrieve public Yahoo Finance market, company, financial, ownership, and analyst data" names the domain and one concrete action across five data categories, but offers only a single verb rather than the several distinct actions of the 4/5 anchors. It exceeds bare domain-naming (score 2) by enumerating concrete data categories, yet is not comprehensive in actions.

3 / 5

Completeness

The description clearly answers "what" (retrieve Yahoo Finance market, company, financial, ownership, and analyst data) but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The "what" is specific rather than vague, so score 2 does not apply.

3 / 5

Trigger Term Quality

"Yahoo Finance", "market", "financial", "ownership", and "analyst" give good natural keyword coverage anchored by the strong trigger "Yahoo Finance". Common user phrasings like "stock", "ticker", "quote", "price", and "earnings" are missing, so it falls short of the comprehensive synonym coverage of score 5 but is noticeably above the sparse keyword set of score 3.

4 / 5

Distinctiveness Conflict Risk

Keying entirely to a single named source ("public Yahoo Finance ... data through authorized access") establishes a clear niche with distinct triggers and minimal conflict risk with other skills. It is far more specific than the "Works with PDF and Word document files" level of score 4.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

KunAgent/Kun

Path

resources/bundled-skills/yahoo-finance/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.