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.

57

Quality

66%

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

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 a well-organized, concise strategy spec with executable formulas and useful pitfalls. Its main gap is the absence of a complete copy-paste example script assembling the formulas into a runnable signal function.

DimensionReasoningScore

Conciseness

The body is lean with inline formulas, a compact parameter table, and non-obvious pitfalls; it assumes competence and avoids explaining basic concepts, with only minor phrasing that could be trimmed.

4 / 5

Actionability

Provides concrete, executable formulas ('returns.rolling(hv_window).std() * sqrt(252)', percentile expression), a parameter table with defaults, and a signal convention; falls short of 5 because no fully assembled copy-paste example script is included.

4 / 5

Workflow Clarity

The Signal Logic is a clear numbered sequence (compute HV, percentile rank, generate signal) with edge-case handling in Common Pitfalls (warm-up fillna); not a 5 because there is no explicit validate/retry loop, though the single-purpose nature makes one less critical.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with no need for external references and well-organized section headers (Purpose, Signal Logic, Key Implementation Details, Parameters, Common Pitfalls, Dependencies, Signal Convention); per the simple-skill guideline this earns a 5.

5 / 5

Total

17

/

20

Passed

Description

53%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 clearly states what the strategy does but lacks an explicit 'Use when...' trigger clause, capping completeness and trigger-term quality. It is reasonably specific and distinct within its quant-strategy niche.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building volatility mean-reversion strategies on OHLCV data or when the user mentions vol regimes, HV percentile, or vol expansion/contraction.'

Include natural synonyms a user might say ('vol regime', 'vol expansion', 'vol contraction') alongside 'historical volatility (HV)' to broaden trigger coverage.

Tighten 'Suitable for any OHLCV data' into a concrete when-to-use statement so the 'when' is explicit rather than implied.

DimensionReasoningScore

Specificity

Names the domain ('volatility strategy') and 1-2 concrete actions ('Trades mean reversion based on percentile ranking of historical volatility'), but coverage is not comprehensive enough for a 4.

3 / 5

Completeness

The 'what' is clear, but the only 'when' cue is 'Suitable for any OHLCV data', which is a data-applicability note rather than explicit trigger guidance; per the rubric a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant domain keywords ('volatility', 'mean reversion', 'historical volatility (HV)', 'OHLCV') but misses common variations/synonyms such as 'vol regime', 'vol expansion/contraction', or file/data type phrasings.

3 / 5

Distinctiveness Conflict Risk

The volatility mean-reversion-via-percentile-ranking niche is mostly distinct from other strategy skills, with only minor overlap risk with related momentum/regime strategies.

4 / 5

Total

13

/

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.

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.