CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

price-history

Get historical price data (OHLCV) for a stock. Use when user asks about price history, historical data, past performance, price over time, or needs data for chart analysis.

Quality

87%

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

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.

A lean, actionable, well-structured body for a simple single-command skill: the executable command, full argument reference, and output contract are all present. The only improvements are a concrete example invocation and trimming the Timezone section that duplicates the script's built-in behavior.

Suggestions

Add one copy-paste-ready example invocation (e.g., `uv run python scripts/history.py AAPL --period 1y --interval 1d`) so the common case is fully concrete.

Trim or merge the Timezone section: the generated_at and data_delay fields are already added automatically by scripts/history.py, so re-stating them as requirements is redundant.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with no concept explanations, but the Timezone section restates output requirements ("must include generated_at ... and data_delay fields") that scripts/history.py already emits automatically, a minor instance of over-explanation.

4 / 5

Actionability

The command `uv run python scripts/history.py SYMBOL [--period PERIOD] [--interval INTERVAL]` is executable with a uv-fallback note and complete argument/defaults documentation, but no concrete example invocation with a real symbol is shown and the output is described rather than demonstrated.

4 / 5

Workflow Clarity

This is a simple, single-purpose, read-only skill and the single action (run the command, parse the JSON, summarize movements) is unambiguous, with the environment-fallback note acting as a light checkpoint; no destructive or batch operations require validation.

5 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections (Instructions, Arguments, Output, Dependencies, Timezone) and no need for external references; the single referenced path, scripts/history.py, exists in the bundle.

5 / 5

Total

18

/

20

Passed

Description

86%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 strong description: clear what-and-when structure with explicit, natural trigger phrases in third-person imperative style. The only gaps are single-action specificity and slightly broad chart-analysis triggers that risk minor overlap with related skills.

Suggestions

Add one or two more concrete actions (e.g., resample to different intervals, return data for charting) to lift specificity beyond a single fetch action.

Narrow the "needs data for chart analysis" trigger or tie it explicitly to historical OHLCV data to reduce overlap with general charting or quote-fetching sibling skills.

DimensionReasoningScore

Specificity

"Get historical price data (OHLCV) for a stock" names the domain and one concrete action with the data shape specified, but lists no additional actions, matching the 1-2-concrete-actions anchor rather than the several-actions anchors.

3 / 5

Completeness

It explicitly answers both what ("Get historical price data (OHLCV) for a stock") and when ("Use when user asks about price history, historical data, past performance...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"price history, historical data, past performance, price over time, or needs data for chart analysis" covers the natural user phrasings with synonyms; file extensions are inapplicable to this domain, so coverage is comprehensive.

5 / 5

Distinctiveness Conflict Risk

Historical OHLCV fetching is a clear niche, but triggers like "price over time" and "chart analysis" could mildly overlap with sibling trading-skills (quotes, charting), fitting the minor-overlap anchor rather than minimal conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

staskh/trading_skills

Path

.claude/skills/price-history/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.