CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/drawdown-circuit-breaker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, actionable, and well-organized with real executable commands and a complete output schema, supported by a one-level-deep reference bundle. The main gap is the absence of an explicit validate-and-retry feedback loop in the workflow.

Suggestions

Add an explicit validation/feedback step (e.g., on malformed or PARTIAL data quality, inspect the offending thesis file, correct it, and re-run) to raise workflow clarity to the top anchor.

Document how a caller should react to each data_quality value (OK, PARTIAL, EMPTY_STATE) so the gate behavior after a degraded run is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and structured with executable CLI commands, a config snippet, and a concrete output example, with no padding explaining concepts Claude already knows.

3 / 3

Actionability

It provides fully executable `python3 ...` commands with real flags, a complete JSON config example, and a copy-paste-ready output schema, matching the executable-and-complete anchor.

3 / 3

Workflow Clarity

A clear four-step sequence with graceful-degradation and data-quality checkpoints is present, but there is no explicit validate→fix→retry feedback loop, so it sits just below the top anchor.

2 / 3

Progressive Disclosure

SKILL.md is an overview that points one level deep to a confirmed reference (references/circuit_breaker_framework.md) and script (scripts/check_circuit_breaker.py), both of which exist, keeping detail appropriately externalized.

3 / 3

Total

11

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-niched with a clear third-person statement of what the skill does. It is held back by an absent explicit "Use when…" trigger clause and limited coverage of natural user phrasings.

Suggestions

Add an explicit "Use when …" clause naming natural trigger phrases (e.g., before sizing a new swing trade, after consecutive losses, when reviewing daily/weekly/monthly loss limits).

Include common user-facing phrasings such as "losing streak", "drawdown limit", and "risk cooldown" alongside the technical terms to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names concrete actions ("Evaluate account-level drawdown circuit breaker rules", "decide whether new trade risk is allowed") and enumerates specific inputs (realized P&L, losing-streak cooldowns, weekly/monthly drawdown limits), matching the multiple-specific-actions anchor.

3 / 3

Completeness

"What" is clearly stated, but "when to use it" is only weakly implied; there is no explicit trigger clause, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Relevant domain keywords are present (drawdown, circuit breaker, losing-streak, P&L) but phrased as a capability with no explicit "Use when…" trigger and limited coverage of phrasings a user would naturally say, fitting the some-relevant-keywords-but-missing-variations anchor.

2 / 3

Distinctiveness Conflict Risk

The account-level drawdown circuit breaker tied to trader-memory-core state is a clear niche with distinct triggers, and the third-person voice keeps it unlikely to fire for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tradermonty/claude-trading-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.