CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

options-strategy

Options strategy framework supporting Black-Scholes pricing, Greeks analysis, and multi-leg backtesting. Suitable for cryptocurrency and equity options.

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-strategy/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 body is strong on concrete, engine-specific guidance — interface format, config schema, examples, and pitfalls are all actionable — but it pads token budget with standard finance textbook material, never sequences the run workflow explicitly, and references an example engine file that is not in the bundle. Trimming known-concept sections and fixing the dangling reference are the highest-leverage improvements.

Suggestions

Replace the Black-Scholes formula block and the Greeks definitions table with one line each (e.g., "European BS pricing with historical-vol-as-IV approximation; portfolio Greeks output daily") and keep only the engine-specific deviations from textbook assumptions.

Add a numbered workflow section (write code/signal_engine.py → create config.json with engine "options" → run the backtest → review artifacts/equity.csv, greeks.csv, trades.csv) including the command to invoke the runner.

Ship the promised example_signal_engine.py in the bundle (or remove/redirect the reference) and add one minimal runnable generate() implementation for a single covered-call signal.

DimensionReasoningScore

Conciseness

The engine-specific sections (interface, config, artifacts, pitfalls) are tight, but "BS Model Principles" spells out the Black-Scholes formula with S/K/T/r/sigma definitions and "Greeks Meaning and Usage" defines Delta/Gamma/Theta/Vega — textbook finance Claude already knows, so the body could be noticeably trimmed. More than minor padding (keeps it below 4), but most sections do earn their tokens (keeps it above 2).

3 / 5

Actionability

Provides the exact SignalEngine instruction dict format, a concrete iron condor signal example, a complete config.json with field-by-field explanation, the artifact file listing, and the options_pricing tool call format — mostly executable guidance. Minor gaps: no runnable generate() implementation, the referenced example_signal_engine.py is absent from the bundle, and no command for actually invoking the backtest runner.

4 / 5

Workflow Clarity

The workflow (write code/signal_engine.py → set config.json with engine "options" → run → inspect artifacts/) is only implicit in section order, never sequenced explicitly, and the doc never shows how to launch the runner — matching 'sequence present but checkpoints missing or implicit'. Each step's details are well defined, so it stays above the many-gaps level of 2.

3 / 5

Progressive Disclosure

The single file is cleanly sectioned and navigable, but it points to "example_signal_engine.py next to this file" which does not exist in the bundle (a dangling reference), and concept-primer material (BS model, Greeks table) that could live in a reference file is inlined. Good structure is undermined by the broken external pointer, placing it between the 3 and 4 anchors but with the reference failure pulling it to 3.

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 is specific, in third person, and uses distinctive domain terminology, but it lacks any explicit 'Use when...' trigger guidance and misses several natural trigger phrases (option trading, hedging, strategy names). Adding a when-to-use clause would lift it from good to excellent.

Suggestions

Add an explicit trigger clause, e.g.: "Use when backtesting option strategies, computing option prices or Greeks, or working with covered calls, straddles, iron condors, or other multi-leg structures."

Include the natural terms users actually say for these tasks — "option trading", "hedging", "volatility trading", and named strategies (covered call, iron condor, straddle) — to broaden trigger coverage.

Consider mentioning the concrete outputs (equity/metrics/trades/greeks artifacts) to sharpen the 'what' beyond the three current capability phrases.

DimensionReasoningScore

Specificity

Lists three concrete capabilities — "Black-Scholes pricing, Greeks analysis, and multi-leg backtesting" — in third person, which matches 'several specific actions; minor gaps in coverage'. Not 5 because coverage isn't comprehensive (no mention of the hedging/spread strategy types the skill actually supports); not 3 because it names more than 1-2 actions.

4 / 5

Completeness

The 'what' is clear (BS pricing, Greeks analysis, multi-leg backtesting), but there is no 'Use when...' or equivalent explicit trigger guidance — "Suitable for cryptocurrency and equity options" states an asset-class boundary, not when to invoke the skill. Per the judging guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "Options strategy", "Black-Scholes", "Greeks", "backtesting", "cryptocurrency and equity options" — terms a user with this need would plausibly say. Missing common variations like "option trading", "hedging", or strategy names (iron condor, straddle), so it falls short of the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

A clear options niche with distinctive terms (Black-Scholes, Greeks, multi-leg) makes wrong-skill triggering unlikely, matching 'mostly distinct; minor overlap risk'. The generic word "backtesting" creates minor overlap with general backtesting/quant skills, keeping it below the clear-niche 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

Path

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