BF options-strategy-advisor
Options trading strategy analysis and simulation tool. Provides theoretical pricing using Black-Scholes model, Greeks calculation, strategy P/L simulation, and risk management guidance. Use when user requests options strategy analysis, covered calls, protective puts, spreads, iron condors, earnings plays, or options risk management. Includes volatility analysis, position sizing, and earnings-based strategy recommendations. Educational focus with practical trade simulation.
Options trading strategy analysis and simulation tool.
As a process F 45/100 · Will not run — References files that are not bundled: references/strategies_guide.md, references/greeks_explained.md, references/volatility_guide.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 7120 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/strategies_guide.md - warning
missing-refreference to a missing file: references/greeks_explained.md - warning
missing-refreference to a missing file: references/volatility_guide.md - warning
missing-refreference to a missing file: scripts/strategy_analyzer.py - warning
missing-refreference to a missing file: scripts/earnings_strategy.py
Process rating: all ten parameters 45/100
- 0Tools and files. 5 referenced file(s) missing: references/strategies_guide.md, references/greeks_explained.md, references/volatility_guide.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 7120 tokens
- 85Steps. 115 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 477: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 115 items
- +3Output format is stated explicitly
- +4Has examples (32 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.