options-strategy

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

Quality

73%

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%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized single-file skill with concrete interfaces and examples, but it pads in textbook concepts and lacks an explicit sequenced workflow or any progressive disclosure into separate reference files.

Suggestions

Remove or condense the BS formula derivation and Greeks definitions — Claude already knows these — keeping only the engine-specific notes (synthetic-data mode, historical-volatility substitution).

Add an explicit numbered workflow (write SignalEngine -> create config.json -> run backtest -> inspect artifacts/) with a validation/check step.

Move the strategy-type table, Greeks reference, and pitfalls into separate reference files under references/ and link to them from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but includes textbook material Claude already knows — the full Black-Scholes formula derivation with 'Where S = underlying price...' and a Greeks table defining Delta/Gamma/Theta/Vega — which could be tightened.	2 / 3
Actionability	It provides fully executable, copy-paste-ready guidance: the SignalEngine class with generate method, the complete instruction dict format, a concrete iron condor example, a full config.json, the artifact file listing, and the pricing tool call format.	3 / 3
Workflow Clarity	An implied workflow (write SignalEngine, set config.json, run backtest, inspect artifacts) is discernible, but steps are not explicitly sequenced and there are no validation checkpoints for what is effectively a multi-step process.	2 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but the ~179-line skill is entirely inline in a single SKILL.md with no bundle files and no references; content such as the strategy reference, Greeks table, and pitfalls could be split out.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 specific, third-person description with good natural trigger terms and a clear niche, but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 2.

Suggestions

Add an explicit 'Use when ...' clause, e.g. 'Use when backtesting option portfolio strategies, analyzing Greeks exposure, or pricing options with Black-Scholes.'

Expand the trigger terms to include common variations users might say, such as 'options backtesting', 'Greeks sensitivity', or 'option pricing analysis'.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities — 'Black-Scholes pricing', 'Greeks analysis', and 'multi-leg backtesting' — rather than vague language, matching the anchor for listing several specific actions.	3 / 3
Completeness	It clearly states what the skill does but offers no 'Use when...' clause or equivalent trigger guidance; 'Suitable for cryptocurrency and equity options' describes scope, not when to invoke it, so completeness is capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	It covers natural terms a user would actually say — 'options strategy', 'Black-Scholes', 'Greeks', 'backtesting', 'cryptocurrency and equity options' — giving good coverage rather than just a few keywords.	3 / 3
Distinctiveness Conflict Risk	The options-strategy niche with BS pricing and multi-leg backtesting is clearly distinguishable from other skills and unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 12 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: 8643fcd

Reviewed: 2 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.