CtrlK
BlogDocsLog inGet started
Tessl Logo

stocks

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

62

Quality

75%

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 ./optional-skills/finance/stocks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary lean, executable SKILL.md: concrete commands, honest pitfalls, and a verification step, with the bundle correctly wired. The two real defects are the Quick Reference/Commands redundancy and an incorrect multi-symbol crypto example that would error against the actual script.

Suggestions

Fix the crypto documentation: the script accepts one symbol per call, so change "crypto SYMBOL [SYMBOL2 ...]" and "python $SCRIPT crypto BTC ETH SOL" to single-symbol usage (e.g. "crypto BTC") and mention the --vs option.

Merge the Quick Reference code block into the Commands section (or replace per-command prose with the annotated block) to remove the duplicated invocation examples.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of what stocks or APIs are, every section (When to Use, Prerequisites, Commands, Pitfalls, Verification) earns its place. It sits at 4 rather than 5 because the "Quick Reference" code block substantially duplicates the "Commands" section that immediately follows it, a small redundancy that could be trimmed.

4 / 5

Actionability

Guidance is copy-paste ready: a full script path invocation ("python $SCRIPT quote AAPL"), per-command syntax, expected JSON output, and a concrete verification command — matching anchor 5. It drops to 4 because one documented example is wrong: the body shows "crypto SYMBOL [SYMBOL2 ...]" and "python $SCRIPT crypto BTC ETH SOL", but the bundled script's crypto subcommand accepts a single symbol (argparse rejects extra positionals), so that example fails as written.

4 / 5

Workflow Clarity

This is a simple, single-action, read-only skill and the invocation is unambiguous, so the simple-skill exception applies. The "Verification" section gives an explicit expected outcome ("a JSON object with symbol: \"AAPL\" and a numeric price field") and the Pitfalls section provides error-recovery guidance (rate-limit delays, null crumb fields backfilled via ALPHA_VANTAGE_KEY), so it does not fall to 4 on missing checkpoints.

5 / 5

Progressive Disclosure

The bundle is a single script (scripts/stocks_client.py) and every reference to it in the body resolves to that real file, one level deep. The body is ~80 well-organized lines with clear section headers and no content that belongs in a separate reference file — a 5-command CLI doc is appropriately inline, matching the well-organized-sections standard for skills needing no external references.

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 terse, concrete description that names all five capabilities without padding, but it omits any explicit trigger guidance. Adding a "Use when..." clause and a few natural synonyms (stock price, ticker, BTC) would move it into the top tier.

Suggestions

Append a trigger clause, e.g. ". Use when the user asks for a stock price, ticker lookup, price history, crypto price, or side-by-side ticker comparison."

Include natural user phrasings and synonyms such as "stock price", "ticker", "Bitcoin" alongside the current command-noun list.

Use verb-led phrasing ("Fetch stock quotes, price history... via Yahoo Finance") to make the listed capabilities read as actions rather than bare nouns.

DimensionReasoningScore

Specificity

The description names five concrete capabilities — "Stock quotes, history, search, compare, crypto" — covering all of the skill's commands, comparable to anchor 5's multiple specific actions. It falls to 4 because the items are bare nouns with no verbs (unlike "Extract text... fill forms, merge documents"), so the actions are listed rather than fully articulated, and the read-only/data-fetch nature is only implied by "via Yahoo".

4 / 5

Completeness

The "what" is clear (five named capabilities sourced from Yahoo), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description, capping completeness at 3 per the judging guideline. It is a firm 3 rather than 4 because the "when" is entirely absent, not just weakly implied.

3 / 5

Trigger Term Quality

"Stock quotes", "crypto", and "compare" are natural phrases users would say, giving good keyword coverage. Missing natural variations like "stock price", "ticker", "Bitcoin"/"BTC", or "market data" — matching anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Stock quotes... crypto via Yahoo" carves out a clear real-time-market-data niche, distinct from the related valuation skills (dcf-model, comps-analysis, lbo-model). Minor overlap risk remains with other finance/market-data skills, matching anchor 4 (mostly distinct, minor overlap risk) rather than anchor 5's minimal conflict risk since terms like "history" and "search" are generic in isolation.

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