options-strategy

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/options-strategy/SKILL.md

Quality

Content

65%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 highly actionable with complete, executable code and config examples, but it over-explains options concepts Claude already knows and lacks an explicitly sequenced workflow with validation checkpoints. With no bundle files, reference-worthy material is inlined rather than progressively disclosed.

Suggestions

Trim or move the BS formula derivation, Greeks-meaning table, and textbook pitfall explanations to a reference file (e.g. references/bs-model.md) since Claude already knows these concepts.

Add an explicitly numbered quick-start workflow (write SignalEngine -> set config.json engine:'options' -> run backtest -> inspect artifacts) with a validation checkpoint such as verifying greeks.csv and equity.csv are non-empty.

Split detailed reference material (strategy catalog, pitfalls, artifact schema) into one-level-deep referenced files so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient (strategy table, interface code, config, artifacts), but the BS Model Principles formula/variable definitions, Greeks-meaning table, and textbook pitfall explanations (volatility smile, time decay, early exercise) restate concepts Claude already knows.	3 / 5
Actionability	Provides fully executable, copy-paste-ready guidance: the SignalEngine class with full signature/docstring, a complete iron-condor multi-leg example, a full config.json with field explanations, exact artifact filenames, and a concrete pricing-tool call with parameters.	5 / 5
Workflow Clarity	The workflow (write signal_engine.py -> set config.json with engine:'options' -> run -> read artifacts) is inferable but not explicitly enumerated, and validation checkpoints for the batch backtest operation are absent, capping at 3.	3 / 5
Progressive Disclosure	Section headers give clear structure, but no bundle files exist and reference-style material (BS derivation, Greeks primer, pitfalls) is inlined in SKILL.md rather than split into one-level-deep references, so navigation cannot leverage separate files.	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.

The description clearly conveys what the skill does with specific domain capabilities, but lacks an explicit 'Use when...' trigger clause, capping completeness. It is distinct and uses appropriate third-person voice with natural trigger terms.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to backtest option strategies, analyze Greeks, or price options via Black-Scholes for crypto or equity underlyings.'

Broaden trigger-term coverage with synonyms users naturally say, e.g. 'options trading', 'volatility trading', and 'hedging strategies'.

Tighten 'framework supporting' to direct action verbs (e.g. 'Prices options with Black-Scholes, analyzes Greeks, and backtests multi-leg strategies') for stronger specificity.

Dimension	Reasoning	Score
Specificity	Names the options domain and three concrete capabilities ('Black-Scholes pricing', 'Greeks analysis', 'multi-leg backtesting'), exceeding the 1-2 action threshold but framed slightly abstractly via 'framework supporting'.	4 / 5
Completeness	The 'what' is clear, but 'when' is only weakly implied by 'Suitable for cryptocurrency and equity options' (a scope statement) rather than an explicit 'Use when...' trigger clause, capping completeness at 3 per the guideline.	3 / 5
Trigger Term Quality	Includes natural domain terms users would say ('options', 'Black-Scholes', 'Greeks', 'backtesting', 'cryptocurrency', 'equity') with good coverage, though it misses common synonyms like 'options trading', 'volatility', or 'hedging'.	4 / 5
Distinctiveness Conflict Risk	The options-strategy niche with BS/Greeks/backtesting is clearly distinct from generic skills with minimal conflict risk, though the absence of an explicit trigger clause leaves slight overlap with a generic backtesting skill.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: e90b6c6

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.