rebalancing

Bounded rebalancing

First: the agent-guardrails skill must be active and the user's caps set. Never run a strategy without caps.

What I'll ask you for first

Before proposing or placing any trade, collect these — ask for whatever's missing, confirm them back, and don't proceed until all are set:

1. Funding & risk tier — funded amount and tier, so agent-guardrails sizes your caps.
2. Holdings & target weights — the exact tickers and the target % for each.
3. Rebalance band — the drift (e.g. 5 points) that triggers a rebalance.
4. Cadence — on a schedule, or only when the band is breached.
5. Approval threshold — the order size above which you approve each trade by hand.

How it works

Keep holdings at target weights: trim what's grown overweight, top up what's lagged. The user sets explicit targets (e.g. 60/40); as prices drift, the agent brings them back toward target.

What contains it

• Rebalance bands, not constant tuning — only rebalance when a weight drifts past a set band (e.g. 5 points), so noise doesn't generate constant small trades.
• Ambiguity rule — "keep it balanced" is not a spec. Require precise targets; halt and ask if they're missing.
• Approval gate — require sign-off on large rebalances.
• Per-trade cap — bounds the size of any single rebalancing order.

Guardrails before trading

Confirm exact target weights, the drift band, caps, and the approval threshold with the user before placing orders. Do not infer targets from anything other than the user's direct instruction.

This is not financial advice. More: https://secprove.com/trading-agent-safety/rebalancing?utm_source=claude-skill&utm_medium=plugin&utm_campaign=trading-agent-safety