CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stocks

Stock quotes, history, search, compare, crypto via Yahoo.

Quality

79%

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 ./optional-skills/finance/stocks/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 well-structured, highly actionable body: every command is copy-paste executable, outputs are specified, failure modes and their remediations are documented, and a verification step closes the loop. The only notable weakness is redundant repetition of the same invocations across four sections, which costs token efficiency without adding information.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and teaches only non-obvious facts (stdlib-only constraint, crumb-session nulls, rate-limit pitfalls). It misses a 5 because command invocations are duplicated across 'How to Run', 'Quick Reference', the 'Commands' headers, and 'Verification' — trimmable redundancy that keeps it at anchor 4.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance: a concrete script path, a Quick Reference block covering all five commands including flags ('history NVDA --range 6mo'), per-command syntax with expected output fields, and a verification step with the expected result ('symbol: "AAPL" and a numeric price field'). This matches anchor 5's 'specific examples cover the common cases'.

5 / 5

Workflow Clarity

The flow is clear — When to Use → run command → parse JSON → verify — with a Verification section and Pitfalls covering failure modes and remediation (set ALPHA_VANTAGE_KEY to backfill nulls). It is not a 5 because there is no explicit error-recovery loop (e.g., what to do when 'search' returns no matches or a request fails mid-batch), leaving minor validation gaps at anchor 4.

4 / 5

Progressive Disclosure

Sections are well-organized (When to Use, Prerequisites, How to Run, Quick Reference, Commands, Pitfalls, Verification), nothing that belongs in a separate file is inlined, and the single bundle file (scripts/stocks_client.py) is referenced at the correct path one level deep. The skill is small enough that a single self-contained SKILL.md is the appropriate split, matching anchor 5's 'content appropriately split; easy navigation'.

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 concise, specific description that names all five capabilities and the data source, with good domain keywords. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness and slightly weakens trigger coverage and distinctiveness.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks for a stock price, wants to look up a ticker by company name, wants price history/performance over a date range, or asks for a crypto price.'

Include natural user terms as synonyms — 'stock price', 'ticker', 'market data', 'BTC/ETH' — to broaden trigger coverage beyond 'quotes' and 'crypto'.

Briefly elaborate one or two actions (e.g., 'daily OHLCV history' instead of bare 'history') to close the specificity gap toward a 5.

DimensionReasoningScore

Specificity

The description lists several specific capabilities — 'quotes', 'history', 'search', 'compare', 'crypto' — covering the domain's main actions. It falls short of a 5 because the actions are single words whose objects are implied (e.g., 'history' doesn't state OHLCV/price history), matching anchor 4's 'several specific actions; minor gaps in coverage' rather than anchor 5's fully elaborated comprehensive list.

4 / 5

Completeness

The 'what' is clear and multi-capability ('Stock quotes, history, search, compare, crypto via Yahoo'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. This matches anchor 3 ('clear what but when is missing') — not anchor 4, which requires both what and when.

3 / 5

Trigger Term Quality

It includes strong natural domain keywords — 'Stock quotes', 'crypto', 'Yahoo' — that users would plausibly say. A few common natural terms are missing ('price', 'ticker', 'market data'), so it fits anchor 4 ('good keyword coverage; a few natural terms missing') rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The phrase carves a clear live-market-data niche via Yahoo, mostly distinct from related finance skills. There is minor overlap risk ('compare' could collide with a comps-analysis skill; 'history' and 'search' are generic words), fitting anchor 4 rather than anchor 5, whose example includes distinct explicit trigger phrases.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/finance/stocks/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.