菜单
Single source of truth for trading session P&L, per-trade risk cap, and daily drawdown kill-switch. Always called by bybit-trade before any order; also exposes status/init/open/close subcommands. Use for "what's my P&L / am I within risk limits / reset my session". Stateful, no network, no API keys.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Pick the best StrategyFactory strategies using a multi-factor composite score (profit factor + sharpe + drawdown + recency + sample size). Use whenever the user asks "what's the best strategy on SF / pick me the top N / find me bangers / which strategies should I deploy". Returns a ranked shortlist with per-factor breakdown so the agent can explain WHY each pick made it. Read-only.
Deploy a StrategyFactory strategy as a copy bot on one of your connected exchanges. Use only after the user has explicitly chosen a strategy (typically via sf-best-pick / sf-market-fit / sf-profit-factor) and named the target exchange and sizing. Dangerous — creates a live bot that places real orders. Always confirm with the user before invoking.
Diagnose whether a strategy's edge is alive, softening, decaying, or dead — by comparing forward-test vs backtest profit factor / win rate and 7d vs 30d vs 90d recency. Use when the user asks "is this strategy still working / is the edge alive / is X dying / health-check this strategy". Read-only.
List HOT StrategyFactory strategies with optional quant filters and sorting. Use when the user asks "what's hot on StrategyFactory", "scan SF for live strategies", "show me HOT strategies with PF > 1.5", or any variant of "what's on the SF leaderboard". Read-only, requires SF_API_KEY/SF_API_SECRET.
Recurring scanner that watches the StrategyFactory HOT leaderboard and surfaces NEW top-N picks as they appear. Designed to be wrapped by the /loop skill (or any cron) — runs one pass per invocation, persists the previous top-N to disk, and emits a delta. Use when the user asks "keep an eye on SF for new winners / monitor the leaderboard / alert me when a new top edge shows up / find me new bangers automatically".
Recurring health watch for deployed bots. One invocation = one pass. Flags decaying / dead bots, can auto-pause them, persists a log so consecutive runs don't double-fire. Pair with the /loop skill for an always-on roster cleaner. Use when the user asks "watch my bots for edge decay automatically / auto-pause dying bots / kill dead edges on a loop / monitor roster health".
| name | risk-guard |
| description | Single source of truth for trading session P&L, per-trade risk cap, and daily drawdown kill-switch. Always called by bybit-trade before any order; also exposes status/init/open/close subcommands. Use for "what's my P&L / am I within risk limits / reset my session". Stateful, no network, no API keys. |
Stateful session tracker. Records every trade, enforces the per-trade risk
cap and daily drawdown limit, and acts as a veto gate for bybit-trade.
bybit-trade before every order (not by the user)All subcommands accept --state-file PATH (default: ~/.claude/skills/risk-guard/state.json).
# Start a session (overwrites existing state after confirmation)
python risk-guard/guard.py init --equity 500 \
[--per-trade-risk-cap 25] [--daily-drawdown-limit 150]
# Veto gate — exit 0 if allowed, exit 2 if blocked
python risk-guard/guard.py check --risk-usd 25
# Record an opened position (called by bybit-trade after a successful order)
python risk-guard/guard.py open \
--order-link-id clive-SOLUSDT-1719000000000 \
--symbol SOLUSDT --side long \
--qty 11.2 --entry 148.20 --sl 145.97 --tp 151.16 --risk-usd 25
# Close it
python risk-guard/guard.py close \
--order-link-id clive-SOLUSDT-1719000000000 \
--exit 151.16 --realized-pnl 33.15
# Human-readable or JSON status
python risk-guard/guard.py status [--json]
check exits 2 with an explanation in stderr if ANY of:
init first)realized_pnl <= -daily_drawdown_limit (drawdown kill-switch)risk_usd > per_trade_risk_cap (this trade would breach the per-trade cap)There is no override flag. This is intentional — bybit-trade invokes
check as a subprocess and treats any non-zero exit as a hard veto.
Human-readable JSON. Open it. Read it. Don't trust.
{
"session_id": "2026-04-22T15:00:00Z",
"started_at": "2026-04-22T15:00:00Z",
"equity_start": 500.0,
"realized_pnl": 0.0,
"per_trade_risk_cap": 25.0,
"daily_drawdown_limit": 150.0,
"trades": [],
"open_positions": []
}