SKILLEMALL.ai
GitHub ↗ RU Sign in

AB drawdown-circuit-breaker

Evaluate account-level drawdown circuit breaker rules from trader-memory-core state and decide whether new trade risk is allowed today. Uses realized P&L, losing-streak cooldowns, and weekly/monthly drawdown limits without any external API.

tradermonty/claude-trading-skills Agent Skills author: tradermonty 8 files · 5 scripts body ≈ 2 075 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Evaluate account-level drawdown circuit breaker rules from trader-memory-core state and decide whether new trade risk is allowed today.

As a process B 67/100 · Nearly there — weak spots: when it triggers, progress reporting

AnalyzerFinancePersonal productivitytype 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
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
B
67/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Failures and branches w 10
50
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: 8. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 44, 171): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 67/100

    • 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
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 16 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2075 tokens
    • 100Running it twice. No mutating operations

    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)
    • -31 of 2 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 240: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 16 items
    • +3Output format is stated explicitly
    • +4Has examples (5 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)

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