risk-management
Skill0 starsChanged 4 months agoMITView on GitHub
Position sizing, drawdown control, and correlation management for crypto trading. Use when designing trade execution, sizing logic, portfolio allocation, or risk gates.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- grace-method/grace-plugintheir own version, first seen Oct 25, 2026
- peterbamuhigire/proposal-skillstheir own version, first seen Oct 17, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
- aws-solutions/konductortheir own version, first seen Sep 23, 2026
- Serennity007/claude-trading-skills-67their own version, first seen Aug 25, 2026
Used with
Projects with it also use sentiment-analysis.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillsentiment-analysis
Use when a director of product asks for the fictional sentiment split and recent excerpts.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- vivy-yi/xiaohongshu-skills★ 455same name
- agiprolabs/claude-trading-skills★ 366same name
- travisjneuman/.claude★ 106same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- abinauv/business-consulting★ 28same name
- aws-solutions/konductor★ 11same 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
6 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 repository11 other files it gives its agents.
- advanced-sql-timescaleSkill
- backtesting-disciplineSkill
- crypto-liquidity-flowSkill
- fastapi-best-practicesSkill
- llm-integrationSkill
- market-microstructureSkill
- qdrant-vector-dbSkill
- redis-patternsSkill
- senior-prompt-engineerSkill
- strategy-optimizationSkill
- websocket-realtimeSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Use alongside [[backtesting-discipline]] (drawdown metrics) and [[market-microstructure]] (liquidation/funding signals).
“Common” is measured: kept by at least 6 in 10 of the 14 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
Position sizing
- Risk per trade — fixed fraction of equity at risk (e.g. 0.5–2%), defined by stop distance:
size = (equity * risk%) / (entry - stop). - Volatility scaling — size inversely to ATR / realized vol so each position contributes similar risk.
- Never size by gut or fixed notional in a volatile market.
Drawdown gates
- Hard max-drawdown limit → halt new entries when breached (e.g. -20% peak-to-trough).
- Daily loss limit → stop trading for the day after N% loss.
- Reduce size after consecutive losses; restore gradually.
Correlation
- Crypto alts are highly correlated to BTC. Treat correlated positions as one aggregate exposure.
- Cap total directional exposure across correlated pairs, not per-symbol.
- Watch funding/liquidation cascades — correlations spike to 1 in crashes.
Leverage
- Futures: account for liquidation price, funding cost, and that liquidation ≠ stop (slippage + fees).
- Lower leverage in high-vol regimes.
Use alongside [[backtesting-discipline]] (drawdown metrics) and [[market-microstructure]] (liquidation/funding signals).
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.