- Home
- Skills
- Trading & Investing
- daily loss lock system
daily loss lock system
Architect and deploy automated risk controls, daily loss limits, and shutdown triggers for trading bots.
$5
Works with the AI Agents you already use
daily loss lock system
Example session with this skill installed
Design a risk management system for a Python crypto bot with a $500 daily loss limit and a 3-trade max per session. Include a 30-minute cooldown after 2 consecutive losses.
- Read your context and instructions
- Compiled the daily loss lock
I will generate a daily-loss-lock-system configuration.
Risk Engine Logic
- Hard Stop: $500 (Liquidate all + Lock)
- Trade Limit: 3 round-trips
- Cooldown: 30m after 2 losses
- State Store: persistent_risk_state.json
Validation flow: check lock_active -> check cooldown -> check count -> execute.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Emotional trading and revenge entries often lead to account-level catastrophes. Developers building trading bots frequently lack deterministic, persistent risk controls that can forcefully stop a strategy before a single bad session wipes out months of gains.
What it does
- Enforces hard and soft loss stops based on combined realized and unrealized PnL.
- Implements trade-count caps and consecutive loss limits to prevent over-trading.
- Manages mandatory cooldown periods and automated strategy shutdown triggers.
- Tracks risk state across restarts using persistent JSON storage.
- Provides a structured execution flow that validates every entry against current risk exposure.
Frameworks & tools
Designed for integration with trading bot frameworks using REST/WebSocket APIs. Uses JSON for state persistence and YAML for risk configuration.
Why this beats prompting it yourself
Standard prompts often overlook edge cases like partial fills, state persistence across crashes, and unrealized PnL calculation. This skill provides a complete architectural blueprint for a failsafe risk engine, ensuring your bot cannot bypass its own rules during high volatility.
Use cases
- Preventing runaway losses during high market volatility.
- Enforcing discipline for high-frequency trading strategies.
- Protecting prop firm accounts from violating daily drawdown rules.
- Automating emergency liquidations during API or data feed failures.
Known limitations
Requires a persistent storage layer to track state across session restarts. Does not predict market moves or guarantee profitability.
Requires a persistent storage layer for state tracking. Requires accurate, real-time price feeds for PnL calculation.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
Permissions
No special permissions declared or detected