options-strategy

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

Quality

70%

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

68%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 highly actionable — complete interface specs, working config, and concrete examples cover the common cases — and is organized into scannable sections. Weaknesses are the absence of an explicit ordered workflow with validation checkpoints, and sections re-explaining Black-Scholes and Greeks basics that Claude already knows, which spend tokens without adding skill-specific value.

Suggestions

Add a short numbered workflow (write `code/signal_engine.py` → set `engine: "options"` in `config.json` → run the backtest → verify `artifacts/metrics.csv` and `greeks.csv` exist and are populated) so the sequence and verification are explicit.

Move the "BS Model Principles" formula block and the Greeks meaning table into a `references/pricing.md` and keep only the engine-specific deviations (historical-vol proxy for IV, European-only exercise) in SKILL.md.

Trim the generic textbook framing in "Common Pitfalls" (volatility smile definition, theta-decay nonlinearity) to one-line caveats, preserving only the engine-specific consequences.

Dimension	Reasoning	Score
Conciseness	Interface specs, config examples, and tables are tight, but the "BS Model Principles" formula block and the Greeks "Meaning and Usage" table re-teach textbook finance Claude already knows. Not 4: the over-explanation is more than minor — only the engine-specific caveats (historical-vol proxy, European-only) earn their tokens.	3 / 5
Actionability	Fully executable end-to-end: complete `SignalEngine.generate` spec, a copy-paste iron-condor instruction, a full `config.json` with every key field explained (including `same_day_fill` and `default_iv` edge behavior), artifact file descriptions, and a concrete `options_pricing` tool invocation.	5 / 5
Workflow Clarity	Sections imply a flow (write signal engine → set `engine: "options"` → run → inspect artifacts) but no ordered step list exists and no validation/verification step tells the agent how to confirm the run worked or diagnose failures. Not 4: checkpoints are implicit rather than listed; the `engine`-must-be-`"options"` note is the only checkpoint-like guidance.	3 / 5
Progressive Disclosure	A single ~180-line file with clear, well-ordered sections and no bundle files to navigate; all content is reachable at one level. Not 5: textbook material (BS formulas, Greeks definitions, common pitfalls) could be split into a reference file, keeping SKILL.md a leaner overview.	4 / 5
	Total	15 / 20 Passed

Description

58%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 states concrete capabilities in proper third-person voice and occupies a distinct niche, but it lacks an explicit "Use when..." trigger clause and natural trigger keywords (strategy names like covered call or straddle, "options trading"). Adding a trigger sentence with user-natural phrases would raise both completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to backtest option strategies (covered calls, straddles, iron condors, butterflies) or analyze option pricing and Greeks."

Include natural user-facing keywords and synonyms such as "options trading", "option spreads", and named strategies (straddle, strangle, iron condor, butterfly) alongside the technical terms.

Replace the hedged "Options strategy framework supporting" with direct concrete verbs (e.g. "Backtests multi-leg option strategies...") to sharpen specificity.

Dimension	Reasoning	Score
Specificity	"Black-Scholes pricing, Greeks analysis, and multi-leg backtesting" lists several concrete, specific capabilities in third person. Not 5: "framework supporting" hedges and coverage of concrete actions misses strategy construction/analysis variants.	4 / 5
Completeness	The "what" is clear (Black-Scholes pricing, Greeks analysis, multi-leg backtesting), but there is no "Use when..." clause; "Suitable for cryptocurrency and equity options" is a domain qualifier rather than an explicit trigger, capping completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Terms like "Black-Scholes", "Greeks analysis", "backtesting" are relevant but lean technical; natural user phrases such as "options trading", "covered call", "straddle", "iron condor" are absent. Not 4: keyword coverage lacks common synonyms and user-facing variations.	3 / 5
Distinctiveness Conflict Risk	Options backtesting with BS pricing and Greeks is a clear niche unlikely to trigger the wrong skill. Not 5: minor overlap risk with general quant/backtesting or crypto-trading skills since no strategy-type triggers distinguish it.	4 / 5
	Total	14 / 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: 251b094

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.