CtrlK
BlogDocsLog inGet started
Tessl Logo

volatility

Volatility strategy. Trades mean reversion based on percentile ranking of historical volatility (HV). Suitable for any OHLCV data.

58

Quality

67%

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 ./agent/src/skills/volatility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a tight, well-structured strategy spec with clear signal logic and useful pitfall notes. Its main gap is actionability: it gives formula fragments rather than a complete, executable implementation.

Suggestions

Provide one complete, copy-paste-ready pandas function that computes the signal end-to-end (including the fillna handling noted in Pitfalls) instead of inline formula fragments.

Show a short runnable example with sample OHLCV input and expected signal output so the convention (1/-1/0) is verifiable.

Optionally note how the signal feeds position sizing or backtesting to clarify the boundary of this skill's responsibility.

DimensionReasoningScore

Conciseness

The body is lean and efficient, assuming Claude's knowledge of pandas and finance; formulae are given inline (e.g. 'returns.rolling(hv_window).std() * sqrt(252)') with no padded explanations, so every token earns its place.

3 / 3

Actionability

It provides concrete formulae and a parameters table with defaults, but these are code fragments rather than a complete, copy-paste-ready executable block, leaving key implementation details (full signal function, fillna handling) implicit.

2 / 3

Workflow Clarity

Signal Logic is a clear 3-step sequence (compute HV, percentile-rank, generate signal) with threshold rules and an edge-case note (fillna before lookback fills); as a simple single-purpose skill the process is unambiguous, qualifying for the top score.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no need for external references, and its well-organized sections (Purpose, Signal Logic, Key Implementation Details, Parameters, Pitfalls, Dependencies, Signal Convention) satisfy the simple-skill top score.

3 / 3

Total

11

/

12

Passed

Description

50%

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 conveys a clear, concrete mechanism but reads as a domain label rather than an invocation guide. It lacks an explicit 'Use when...' trigger, capping its completeness and distinctiveness.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when building or evaluating volatility mean-reversion strategies on OHLCV price data.'

Broaden natural keyword coverage (e.g. 'volatility trading', 'vol regime', 'mean reversion signal') beyond HV/OHLCV jargon.

List the concrete actions the skill supports (compute HV, rank percentiles, emit long/short/stand-aside signals) to lift specificity from a single mechanism to multiple named actions.

DimensionReasoningScore

Specificity

The description names a concrete domain and action ('Trades mean reversion based on percentile ranking of historical volatility (HV)') but describes a single mechanism rather than a list of multiple specific actions, matching the score-2 anchor.

2 / 3

Completeness

It clearly states what the skill does but provides no 'Use when...' trigger clause; 'Suitable for any OHLCV data' describes data applicability rather than when Claude should invoke it, so per guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

It includes relevant keywords like 'volatility', 'mean reversion', 'historical volatility', 'HV', and 'OHLCV data', but these skew toward specialized jargon and miss common natural-language variations a user might say.

2 / 3

Distinctiveness Conflict Risk

The HV-percentile mean-reversion niche is somewhat specific, but 'Suitable for any OHLCV data' is broad and could overlap with many other trading-strategy skills, matching the score-2 anchor.

2 / 3

Total

8

/

12

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.

Validation15 / 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
HKUDS/Vibe-Trading
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.