SKILLEMALL.ai
GitHub ↗ RU Sign in

AB stockbee-setup-fluency-trainer

Build a Stockbee-style setup model book from momentum-burst screener candidates, then update 3-day and 5-day forward outcomes with MFE/MAE, stop-hit status, outcome tags, and cohort statistics. Use when the user wants to study Stockbee Momentum Burst examples, track failed candidates, build setup fluency, review A/B setup quality, or convert screener outputs into a learning loop rather than immediate trade signals.

tradermonty/claude-trading-skills Agent Skills author: tradermonty 9 files · 4 scripts body ≈ 1 280 tokens Open the sourcegithub.com↗ analyzed 32 h ago

Build a Stockbee-style setup model book from momentum-burst screener candidates, then update 3-day and 5-day forward outcomes with MFE/MAE, stop-hit status…

As a process B 75/100 · Nearly there — no weak spots found

GeneratorData and analyticsWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
94
Run on models
none yet
Process rating
B
75/100
Nearly there
Failures and branches w 10
50
Tools and files w 18
60
Result and completion w 14
60
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 9. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 75/100

    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 38 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1280 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress

    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 418: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 38 items
    • +3Output format is stated explicitly
    • +4Has examples (4 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +3All 2 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.