CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

options-advanced

Advanced options strategies: volatility-surface modeling (SABR / Local Vol), dynamic Greeks rebalancing, calendar spreads, volatility arbitrage and skew trading, and option market-making basics.

Quality

68%

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/options-advanced/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 content is dense with genuinely valuable market-specific knowledge and mostly actionable guidance, including concrete tool calls and fully priced examples. Its weaknesses are padding from textbook Greeks definitions, no explicit top-level analysis workflow, and a monolithic single-file structure that inlines material better split into references.

Suggestions

Trim the first-order/second-order Greeks definition tables and the 'intrinsic + time value' primer — Claude already knows these; keep only the market-specific management guidance (hedge frequencies, Zakamouline trigger).

Add a numbered top-level workflow (1. fetch and validate the option chain, 2. build the vol surface via quantlib_call, 3. assess skew/term-structure percentile vs history, 4. select strategy from the framework, 5. set Greeks limits and monitor) so the analysis sequence is explicit.

Move the per-strategy detail (calendar spread, vol arbitrage, skew trades, market-making) into references/ files one level deep, keeping SKILL.md as an overview with clearly signaled links, and remove the unused pandas/numpy/scipy dependency block or add code that uses it.

DimensionReasoningScore

Conciseness

The body inlines textbook definitions Claude already knows ('Delta (Δ) | Sensitivity to underlying price', 'Gamma | Rate of change of Delta', 'option price = intrinsic value + time value'), though much of the rest is genuinely non-obvious market-specific knowledge (A-share skew, liquidity concentration, Zakamouline hedge trigger). Fits anchor 3 (mostly efficient with some unnecessary explanation); not 4 because the basic Greeks tables and overview padding could be trimmed.

3 / 5

Actionability

Provides a concrete copy-paste tool call (quantlib_call with implied_volatility_surface kwargs), numeric entry conditions ('20-30 days before near-month expiry'), fully priced 50ETF trade examples, explicit position limits, and an output report template. Not 5 because SABR calibration and quoting strategy remain conceptual, and the listed pip dependencies (pandas/numpy/scipy) are never used by any code in the skill.

4 / 5

Workflow Clarity

Each strategy carries entry conditions and risk-control checkpoints ('stop loss if loss exceeds 50% of net debit', 'close when term-structure inverts'), but there is no explicit end-to-end sequence (fetch chain -> build surface -> diagnose skew/term structure -> select strategy -> monitor Greeks); the overall process must be inferred. Anchor 3 (sequence present but implicit/fragmented); not 4 because the top-level analysis workflow is never laid out as ordered steps.

3 / 5

Progressive Disclosure

The file is well-sectioned with clear headers, but ~185 lines of dense strategy detail (four full strategies, SABR parameter tables, market-making specifics) are all inlined with no reference files at all, exceeding the simple-skill threshold where sections alone would suffice. Anchor 3 (content that should be separate is inline); not 2 because structure and navigation within the file are good.

3 / 5

Total

13

/

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.

The description clearly and specifically communicates what the skill covers, with strong domain-distinctive terminology and low conflict risk. Its main weakness is the complete absence of a 'when to use' clause, which caps completeness and slightly weakens trigger discoverability.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about options Greeks hedging, implied volatility surfaces, calendar spreads, or volatility/skew arbitrage.'

Include natural synonym phrasings users actually say — 'options trading', 'implied volatility', 'delta hedging', 'vol surface' — to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Lists several specific capabilities ('volatility-surface modeling (SABR / Local Vol), dynamic Greeks rebalancing, calendar spreads, volatility arbitrage and skew trading, and option market-making basics'), matching anchor 4's several-specific-actions-with-minor-gaps. It is not 5 because the items are topic noun-phrases rather than concrete actions and 'market-making basics' is loosely scoped; not 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

The 'what' is clear and comprehensive, but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete and multi-part, not vague.

3 / 5

Trigger Term Quality

Contains good natural keywords a user would say ('options strategies', 'calendar spreads', 'Greeks', 'SABR', 'volatility arbitrage'), but misses common variations such as 'options trading', 'implied volatility', 'delta hedging', or 'vol surface'. Fits anchor 4 (good coverage, a few natural terms missing) rather than 5 (comprehensive synonyms/extensions) or 3 (only 'some relevant keywords').

4 / 5

Distinctiveness Conflict Risk

A clear niche (advanced options / volatility trading) with distinct terms like SABR, Greeks rebalancing, and skew trading; the word 'Advanced' implies a sibling basic-options skill, creating minor overlap risk with a closely related skill. Fits anchor 4 rather than 5's minimal-conflict clear niche.

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

Path

agent/src/skills/options-advanced/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.