risk-management
Skill366 starsChanged 8 months agoMITView on GitHub
Portfolio-level risk controls, drawdown management, exposure limits, and circuit breakers for crypto trading
We split this skill into the rules it gives an agent
13 rules. 0 are common, 12 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Every decision must respect this priority order:
- Distinctive: line 36
Stop opening new positions after daily P&L (realized + unrealized) hits:
- Distinctive: line 78
Treat all meme tokens as a single correlated bucket
- Distinctive: line 116
No trading for 24 hours after hitting daily loss limit
- Distinctive: line 192
Never allocate >5% of account to a single unaudited protocol
- Distinctive: line 198
Verify: locked liquidity, renounced mint authority, holder distribution
- Distinctive: line 202
Don't hold >20% on any single platform or bridge
- Distinctive: line 208
Use priority fees during congestion
- Distinctive: line 221
Treat every PumpFun trade as a potential 100% loss.
- Distinctive: line 226
Never exceed budget: When daily allocation is gone, stop
- Distinctive: line 231
Don't let PumpFun losses affect main portfolio risk limits
- Distinctive: line 234
No stop-losses on PumpFun (assume 100% loss at entry)
- Very specific: line 240
position-sizing: Use risk limits from this skill to constrain position sizes
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Risk Management
Portfolio-level risk controls for crypto and Solana trading. This skill provides frameworks for drawdown management, exposure limits, circuit breakers, and crypto-specific risk considerations.
Risk Management Hierarchy
Every decision must respect this priority order:
- Survival — Never risk account ruin. No single trade, day, or week should threaten your ability to continue trading.
- Capital preservation — Protect what you have. Losses compound geometrically; recovery requires outsized gains.
- Growth — Only after survival and preservation are secured, pursue returns.
Violating this hierarchy (chasing growth at the expense of survival) is the primary cause of account blowups.
Portfolio-Level Controls
1. Maximum Drawdown Limits
Halt trading when portfolio drawdown from equity peak reaches a threshold:
| Account Type | Max Drawdown | Action |
| Conservative | -15% | Full stop, review all strategies |
| Moderate | -20% | Full stop, reduce to minimum size on recovery |
| Aggressive | -25% | Full stop, mandatory cooling period |
Recovery math makes this critical: a -20% drawdown requires +25% to recover. A -50% drawdown requires +100%. See references/drawdown_management.md for the full recovery table.
2. Daily Loss Limits
Stop opening new positions after daily P&L (realized + unrealized) hits:
- Conservative: -3% of account
- Moderate: -4% of account
- Aggressive: -5% of account
Reset at midnight UTC. Three consecutive days hitting the daily limit triggers a weekly halt.
3. Weekly Loss Limits
Reduce size or halt after weekly P&L reaches:
- Reduce size by 50%: -5% weekly loss
- Minimum size only: -7% weekly loss
- Full halt: -10% weekly loss
4. Concentration Limits
Maximum allocation to any single dimension:
| Dimension | Max Concentration |
| Single token (blue chip) | 10% of account |
| Single token (mid-cap) | 5% |
| Single token (small-cap) | 2% |
| Single token (PumpFun/micro) | 0.5% |
| Single sector/narrative | 30% |
| Single strategy | 40% |
5. Exposure Limits
Total deployed capital constraints:
- Normal conditions: 50–80% deployed, 20–50% cash reserve
- Elevated risk: 30–50% deployed
- Drawdown >10%: 20–30% deployed
- Max concurrent positions: 5–10 depending on account size
6. Correlation Management
Crypto assets correlate >0.7 during sell-offs. Effective diversification requires:
- Treat all meme tokens as a single correlated bucket
- Limit total meme exposure to one position-size equivalent
- Diversify across strategies (trend, mean-reversion, scalp), not just tokens
- Monitor rolling correlation and reduce when correlations spike
See references/exposure_limits.md for detailed limits by token type and strategy.
Drawdown Management
Response Framework
| Drawdown | Status | Response |
| 0–5% | Normal | Continue trading at full size |
| 5–10% | Caution | Reduce position sizes by 25–50% |
| 10–15% | Warning | Minimum position sizes only |
| 15–20% | Critical | Halt new trades, manage existing positions only |
| >20% | Emergency | Full stop, review everything before resuming |
Recovery Requirements
| Loss | Required Gain to Recover |
| -5% | +5.3% |
| -10% | +11.1% |
| -15% | +17.6% |
| -20% | +25.0% |
| -30% | +42.9% |
| -40% | +66.7% |
| -50% | +100.0% |
The asymmetry accelerates rapidly. Managing small drawdowns prevents them from becoming catastrophic. See references/drawdown_management.md for the full framework.
Circuit Breakers
Automated controls that restrict trading when conditions are met:
Time-Based
- No trading for 24 hours after hitting daily loss limit
- 48-hour cooling period after weekly loss limit
- Mandatory weekly review day (no new positions)
Loss-Based
- 3 consecutive losses → reduce size 50%
- 5 consecutive losses → minimum size only
- 7 consecutive losses → halt 24 hours, full review
Volatility-Based
- Portfolio volatility >2× rolling average → reduce exposure 50%
- Market-wide liquidation events → pause all new entries
- Individual token volatility spike → exit or tighten stops
Emotional (Self-Assessed)
- Recognize tilt: anger after losses, urge to "make it back"
- FOMO: rushing entries without proper analysis
- Overconfidence: increasing size after a win streak without justification
See references/circuit_breakers.md for implementation details.
Risk Metrics
Value at Risk (VaR)
95th-percentile daily loss estimate using historical returns:
import numpy as np
def historical_var(returns: list[float], confidence: float = 0.95) -> float:
"""Calculate historical VaR at given confidence level."""
sorted_returns = sorted(returns)
index = int((1 - confidence) * len(sorted_returns))
return abs(sorted_returns[index])
# Example: 95% VaR of 3.2% means on 95% of days, loss won't exceed 3.2%Expected Shortfall (CVaR)
Average loss in the worst (1 - confidence)% of scenarios:
def expected_shortfall(returns: list[float], confidence: float = 0.95) -> float:
"""Average loss beyond VaR threshold."""
sorted_returns = sorted(returns)
index = int((1 - confidence) * len(sorted_returns))
tail = sorted_returns[:index]
return abs(sum(tail) / len(tail)) if tail else 0.0Maximum Drawdown
def max_drawdown(equity_curve: list[float]) -> float:
"""Peak-to-trough decline as a fraction."""
peak = equity_curve[0]
max_dd = 0.0
for value in equity_curve:
peak = max(peak, value)
dd = (peak - value) / peak
max_dd = max(max_dd, dd)
return max_ddAdditional Metrics
- Win/loss streak tracking: Detect hot/cold streaks for circuit breaker logic
- Rolling Sharpe ratio: 30-day rolling risk-adjusted returns
- Calmar ratio: Annualized return / max drawdown
- Sortino ratio: Return / downside deviation (penalizes only negative volatility)
Crypto-Specific Risks
Smart Contract Risk
- Never allocate >5% of account to a single unaudited protocol
- Diversify across audited protocols for yield strategies
- Monitor exploit databases and social channels for emerging threats
Rug Pull Risk
- Size inversely with token age: newer tokens get smaller positions
- Verify: locked liquidity, renounced mint authority, holder distribution
- Cross-reference with
token-holder-analysisskill for red flags
Bridge and Custody Risk
- Don't hold >20% on any single platform or bridge
- Self-custody the majority of trading capital
- Budget for bridge fees and delays in execution planning
MEV and Execution Risk
- Budget 1–3% for MEV/slippage on Solana DEX trades
- Use priority fees during congestion
- See
slippage-modelingskill for detailed cost estimation
Correlation Spikes
- In crashes, crypto correlations approach 1.0
- Your "diversified" portfolio may behave as one position
- Stress-test portfolio assuming all positions drop simultaneously
PumpFun Risk Framework
PumpFun and similar meme token platforms require a distinct risk approach:
Core Principle
Treat every PumpFun trade as a potential 100% loss. Size accordingly.
Position Limits
- Per-token maximum: 0.1–0.5 SOL
- Daily PumpFun budget: Fixed allocation (e.g., 2 SOL/day)
- Never exceed budget: When daily allocation is gone, stop
Tracking
- Track PumpFun P&L separately from main portfolio
- Calculate PumpFun win rate and expectancy independently
- Don't let PumpFun losses affect main portfolio risk limits
Risk Adjustments
- No stop-losses on PumpFun (assume 100% loss at entry)
- Take profits aggressively: 2×, 3×, 5× partial exits
- Time-based exit: close within hours, not days
Integration with Other Skills
position-sizing: Use risk limits from this skill to constrain position sizesexit-strategies: Circuit breakers override exit strategies (forced exits)portfolio-analytics: Feed portfolio metrics back for risk assessmentliquidity-analysis: Adjust position limits based on available liquidityslippage-modeling: Factor execution costs into risk calculations
Files
References
references/drawdown_management.md— Drawdown math, response framework, causes, and remediationreferences/exposure_limits.md— Position limits by token type, portfolio limits, correlation managementreferences/circuit_breakers.md— Implementation details for all circuit breaker types
Scripts
scripts/risk_dashboard.py— Portfolio risk dashboard with limit checking and color-coded statusscripts/drawdown_analyzer.py— Equity curve drawdown analysis with response recommendations
Quick Start
# Run the risk dashboard with demo data
python scripts/risk_dashboard.py --demo
# Analyze drawdowns on a demo equity curve
python scripts/drawdown_analyzer.py --demoOther versions16 projects use a version of this.
Word for word · 2
- IngAs8/ClaudeSkill★ 0100% same
- Serennity007/claude-trading-skills-67★ 0100% same
Edited · 0
None found.
Wrote their own version · 14
- vivy-yi/xiaohongshu-skills★ 455same name
- travisjneuman/.claude★ 106same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- abinauv/business-consulting★ 28same name
- aws-solutions/konductor★ 10same name
- peterbamuhigire/proposal-skills★ 8same name
- Dragoon0x/product-skills★ 4same name
- gokulsvision/crewm8-cfo-skills★ 2same name
- lexbeam-software/eu-ai-governance-plugin★ 2same name
- Vaibhavkkm/vkkm-aegis-plugin★ 2same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository67 other files it gives its agents.
- backtraderSkill
- birdeye-apiSkill
- coingecko-apiSkill
- cointegration-analysisSkill
- copy-tradingSkill
- correlation-analysisSkill
- cost-basis-engineSkill
- crypto-tax-exportSkill
- custom-indicatorsSkill
- defillama-apiSkill
- dex-executionSkill
- dex-pool-analysisSkill
- dexscreener-apiSkill
- exit-strategiesSkill
- feature-engineeringSkill
- fixed-incomeSkill
- helius-apiSkill
- impermanent-lossSkill
- jito-bundlesSkill
- kalshi-apiSkill
- kalshi-crypto-index-marketsSkill
- kalshi-weather-marketsSkill
- kelly-criterionSkill
- liquidity-analysisSkill
- lp-mathSkill
- market-microstructureSkill
- market-microstructure-traditionalSkill
- mean-reversionSkill
- mev-analysisSkill
- ohlcv-processingSkill
- options-pricingSkill
- pandas-taSkill
- polymarket-apiSkill
- portfolio-analyticsSkill
- position-sizingSkill
- prediction-market-live-opsSkill
- prediction-market-strategySkill
- pumpfun-mechanicsSkill
- raptor-dexSkill
- regime-detectionSkill
- regulatory-reportingSkill
- rl-executionSkill
- sentiment-analysisSkill
- shredstreamSkill
- signal-classificationSkill
- slippage-modelingSkill
- solana-rpcSkill
- solanatracker-apiSkill
- solana-tx-buildingSkill
- strategy-frameworkSkill
- sybil-detectionSkill
- ta-libSkill
- tax-liability-trackingSkill
- tax-loss-harvestingSkill
- token-economicsSkill
- token-holder-analysisSkill
- trade-accountingSkill
- trade-journalSkill
- trading-visualizationSkill
- vectorbtSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

