BC Options Strategies Lite
Options strategy selector and plain-English guide to 5 core strategies. Tell me your market outlook and I'll point you to the right strategy. Covers covered calls, cash-secured puts, vertical spreads, iron condors, and LEAPS. Free version — upgrade for Greeks management, IV rank guidance, position sizing, and full adjustment playbooks.
As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 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
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (Options Strategies Lite) differs from the folder (options-strategies-lite)
- 65Failures and branches. 3 branches
- 100Tools and files. No external tools needed
- 100Steps. 46 steps
- 100Execution cost. Instruction body is 2663 tokens
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)
- +3Output format is not stated: the model decides each time
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 337: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 46 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.