BF perfect-storm-options-trader
Autonomous but risk-bounded options trading agent spec for the "Perfect Storm" strategy (paper trading only). Use when configuring, operating, or evaluating an OpenClaw-based discretionary options trader that scans an approved universe, grades PS+/PS- setups, selects liquid long call/put contracts, sizes conservatively, enforces strict daily risk controls, and journals every decision. Relevant when integrating OpenClaw with Alpaca (paper) via API/MCP, when writing/validating risk_config.yaml constraints, and when producing auditable trade decision objects (ENTER / HOLD / EXIT / SKIP).
Autonomous but risk-bounded options trading agent spec for the "Perfect Storm" strategy (paper trading only).
As a process F 38/100 · Will not run — References files that are not bundled: references/AGENTS.md, references/risk_config.yaml, scripts/alpaca.mjs
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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5285 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/AGENTS.md - warning
missing-refreference to a missing file: references/risk_config.yaml - warning
missing-refreference to a missing file: scripts/alpaca.mjs
Process rating: all ten parameters 38/100
- 0Tools and files. 3 referenced file(s) missing: references/AGENTS.md, references/risk_config.yaml, scripts/alpaca.mjs
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (perfect-storm-options-trader) differs from the folder (perfect-storm-options-trader-v2)
- 65Failures and branches. 3 branches
- 70Execution cost. Instruction body is 5285 tokens
- 100Steps. 82 steps
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 591: enough signal without eating the budget
- +4Structure: 44 headings
- +3Step-by-step instructions: 82 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.