How do I install the Sf Rebalance skill?

Run npx skillmds@latest add daviddme/sf-rebalance in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sf Rebalance safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sf Rebalance?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sf Rebalance free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sf Rebalance?

daviddme (@daviddme) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sf Rebalance by daviddme — Agent Skill

Name: Sf Rebalance
Rating: 4.2 (5 reviews)
Author: daviddme

Sf Rebalance

Refresh the deployed bot roster — pause decaying bots AND propose fresh top picks to replace them on the same exchanges with the same sizing. Use when the user asks "rebalance my bots / swap losers for winners / refresh the roster / clean up and replace / optimize my deployed strategies". Writes state (pauses) only with --apply; never auto-deploys.

daviddme Updated Sep 22, 2026

File contents

sf-rebalance

The two-step roster refresh. Combines sf-prune (find decaying bots) and sf-best-pick (find replacement strategies) into a single proposal you can scan on stream and execute in one shot.

What it does

Audit every ACTIVE bot's underlying strategy for edge decay.
For each decaying or dead bot, propose a replacement from the current top-N composite-score picks (filtered to bots NOT already in your roster, to avoid duplicates).
Optionally --apply the pauses.
NEVER auto-creates new bots — that's sf-deploy's job. Replacements are surfaced as ready-to-run sf-deploy commands.

Why not auto-deploy?

Pausing a bot is reversible. Creating one isn't quite — you'd have to pause-then-delete (which isn't an endpoint). So this skill stays on the careful side: prune now, propose replacement, let the operator pull the trigger on the new deploy.

When to use

"Rebalance my bots"
"Swap the losers for winners"
"Refresh the roster — kill what's dead, suggest replacements"

How to run

# Pure proposal mode — no changes
python sf-rebalance/rebalance.py [--top-picks N] [--json]

# Pause the dying ones; still only PROPOSES replacements
python sf-rebalance/rebalance.py --apply [--top-picks N]

Output

Two sections:

TO PAUSE
  [decaying] BotName  strategy=X  flags=...
  [dead]     BotName  strategy=Y  flags=...

REPLACEMENT CANDIDATES (run sf-deploy to actually create)
  --strategy slug-a --exchange EX_ID --position percentage --amount 3 --leverage 10
  --strategy slug-b --exchange EX_ID --position percentage --amount 3 --dynamic-leverage

Replacements inherit the pruned bot's exchangeId, position, amount, and leverage mode so the agent can copy-paste straight into sf-deploy.

---name: sf-rebalancedescription: Refresh the deployed bot roster — pause decaying bots AND propose fresh top picks to replace them on the same exchanges with the same sizing. Use when the user asks "rebalance my bots / swap losers for winners / refresh the roster / clean up and replace / optimize my deployed strategies". Writes state (pauses) only with --apply; never auto-deploys.---# sf-rebalanceThe two-step roster refresh. Combines `sf-prune` (find decaying bots) and`sf-best-pick` (find replacement strategies) into a single proposal youcan scan on stream and execute in one shot.## What it does1. Audit every ACTIVE bot's underlying strategy for edge decay.2. For each `decaying` or `dead` bot, propose a replacement from the current top-N composite-score picks (filtered to bots NOT already in your roster, to avoid duplicates).3. Optionally `--apply` the pauses.4. NEVER auto-creates new bots — that's `sf-deploy`'s job. Replacements are surfaced as ready-to-run `sf-deploy` commands.## Why not auto-deploy?Pausing a bot is reversible. Creating one isn't quite — you'd have topause-then-delete (which isn't an endpoint). So this skill stays on thecareful side: prune now, propose replacement, let the operator pull thetrigger on the new deploy.## When to use- "Rebalance my bots"- "Swap the losers for winners"- "Refresh the roster — kill what's dead, suggest replacements"## How to run```# Pure proposal mode — no changespython sf-rebalance/rebalance.py [--top-picks N] [--json]# Pause the dying ones; still only PROPOSES replacementspython sf-rebalance/rebalance.py --apply [--top-picks N]```## OutputTwo sections:```TO PAUSE [decaying] BotName strategy=X flags=... [dead] BotName strategy=Y flags=...REPLACEMENT CANDIDATES (run sf-deploy to actually create) --strategy slug-a --exchange EX_ID --position percentage --amount 3 --leverage 10 --strategy slug-b --exchange EX_ID --position percentage --amount 3 --dynamic-leverage```Replacements inherit the pruned bot's `exchangeId`, `position`, `amount`,and leverage mode so the agent can copy-paste straight into `sf-deploy`.

Frequently asked questions