CtrlK
BlogDocsLog inGet started
Tessl Logo

hedging-strategy

Hedging strategy design (beta hedge / option protection / tail risk / cross-asset hedging), including hedge-ratio calculation and cost evaluation.

56

Quality

71%

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/hedging-strategy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 substantive, domain-rich skill with strong quantitative guidance, useful worked examples, and a concrete output format. Its weaknesses are pedagogical padding around basic option strategies, the absence of explicit validation checkpoints in the workflow, and a monolithic structure with no progressive disclosure despite being ~260 lines.

Suggestions

Move the basic option-strategy definitions (protective put, collar, put spread) and worked instrument examples into a reference file (e.g., references/strategies.md), keeping SKILL.md as an overview — Claude already knows these constructions.

Add an explicit validation checkpoint in the five-step process, e.g., after step 3: 'Verify: hedge coverage × expected move ≈ target loss reduction; recalculate if beta or portfolio value has drifted.'

Trim comment-style pseudocode blocks (tail-risk parameters, cost-benefit framework) into either runnable functions or compact decision tables to make the guidance copy-paste ready.

DimensionReasoningScore

Conciseness

The tables (contract multipliers, margins, annualized costs, correlation regimes) are dense and information-rich, but several sections re-explain concepts Claude already knows — 'Hold the underlying + buy a put option', collar construction, put-spread mechanics, and 'Naturally negatively correlated with an equity portfolio'. The padding is more than minor, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than the level-4 'minor instances' anchor.

3 / 5

Actionability

Most guidance is executable: worked hedge-ratio code with real numbers, a complete output-format template, parameter-selection tables, and a cost-benefit decision framework. It stops short of 5 because several snippets are comment-style pseudocode (tail-risk parameters, the cost-benefit example) or reference undefined variables (portfolio_returns, hedge_returns), so they are not copy-paste ready.

4 / 5

Workflow Clarity

The five-step design process (identify risk → choose instrument → calculate ratio → evaluate cost → monitor/adjust) is clearly sequenced and supported by scenario-to-instrument mapping and decision frameworks. Checkpoints like 'verify hedge coverage against target' are only implicit in step 5 rather than explicit validation steps, which is the minor gap separating it from a 5.

4 / 5

Progressive Disclosure

Headers and section organization are clear, but this is a single ~260-line file with no bundle files, and content that would live well in references (option-strategy definitions, instrument tables, worked 50ETF examples) is fully inlined. It matches 'some structure but content that should be separate is inline' better than level 4, which expects most content appropriately split.

3 / 5

Total

14

/

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 reasonably strong description: domain-specific, concrete about capabilities, and clearly distinct from general finance skills. Its main weakness is the absence of any 'Use when...' trigger guidance, which both caps completeness and leaves activation to keyword luck.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to hedge an existing portfolio, protect against drawdowns or tail risk, or size futures/option hedges.'

Include common user phrasings/synonyms such as 'portfolio protection', 'hedge ratio', 'insurance for my positions', and 'drawdown protection' to broaden natural trigger coverage.

Mention the output deliverable (hedge ratios, cost estimates, execution plans) to sharpen the 'what' and further distinguish it from generic options-trading skills.

DimensionReasoningScore

Specificity

The description names the domain plus several specific actions — 'hedge-ratio calculation and cost evaluation' — across four named sub-areas (beta hedge / option protection / tail risk / cross-asset hedging). It falls short of a 5 because coverage has minor gaps (e.g., execution planning and monitoring, which the body covers, are absent).

4 / 5

Completeness

The 'what' is clear (designs hedging strategies, calculates hedge ratios, evaluates costs), but there is no 'Use when...' clause or equivalent trigger guidance — the 'when' is at best weakly implied. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3; it is not lower because the 'what' is concrete and multi-part.

3 / 5

Trigger Term Quality

'beta hedge', 'option protection', 'tail risk', and 'cross-asset hedging' are natural phrases a user would say when needing this skill, giving good keyword coverage. A few natural variations are missing (e.g., 'portfolio protection', 'drawdown', 'hedge my positions'), keeping it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

'Hedging strategy design' with named sub-strategies carves out a clear niche with mostly distinct triggers. There is minor overlap risk with a generic options-strategy or portfolio-allocation skill (e.g., 'option protection' could also trigger an options skill), so it does not reach the minimal-conflict clarity of a 5.

4 / 5

Total

15

/

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