agentleFS
SKE-LabsSKE-Labs/agent-trading-skills/skills/crypto-trading/altcoin-rotation/SKILL.md

altcoin-rotation

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

Build and test survivorship-aware crypto rotation rankings. Use when allocating among BTC, ETH, and liquid altcoins with relative strength, breadth, liquidity, stress, turnover, and concentration controls.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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
  1. Distinctive:

    Treat the setup as a testable hypothesis, not a prediction.

    line 47
  2. Distinctive:

    NEVER backtest with a present-day survivor list or rank on information unavailable at the rebalance timestamp

    line 55
  3. Distinctive:

    NEVER treat BTC dominance thresholds as universal cycle boundaries

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Altcoin Rotation Strategy

Rank a liquid, survivorship-aware crypto universe and rotate only when relative strength and breadth improve without a BTC stress event.

Rotation Model

InputReproducible measureUse
Relative strengthCandidate/BTC and candidate/ETH total return over frozen lookbacksRank, do not predict
BreadthShare of eligible alts outperforming BTCRequire broad participation
LiquidityMedian dollar volume, spread, depth, listing ageExclude untradeable winners
BTC stressBTC drawdown, realized volatility, and market breadthDe-risk when the common factor dominates
ConcentrationPairwise correlation and BTC betaCap duplicated exposure

Build the universe from assets that were actually tradable at each historical date. Exclude stablecoins, wrapped duplicates, recent listings without sufficient history, and instruments that fail the account's liquidity floor. Do not use today's top coins in an old backtest.

Workflow

  1. Establish the BTC regime from price history, not headlines:
get_candles(symbol="BTC/USD", exchange="binance", interval="1d", count=120)
  1. Measure relative strength on the same timestamps and venue:
get_candles(symbol="ETH/BTC", exchange="binance", interval="1d", count=120)
get_candles(symbol=<candidate_btc_pair>, exchange=<exchange>, interval="1d", count=120)
  1. Rank and gate candidates by predeclared return lookbacks, breadth, liquidity, and correlation. Treat BTC dominance as optional context only when sourced from a consistent, documented series.
  2. Rebalance on a fixed schedule with a no-trade buffer so small rank changes do not create fee churn. Compare the rotation with BTC-only, ETH/BTC, and equal-weight eligible-universe benchmarks.
  3. Report universe date, excluded assets, lookbacks, ranks, breadth, BTC stress state, turnover, expected costs, proposed weights, and the condition that returns the portfolio to its defensive allocation.

Evidence and Validation

  • Treat the setup as a testable hypothesis, not a prediction. Define thresholds, entry, invalidation, and exit before evaluating outcomes.
  • Calibrate on the same instrument, venue, session, and timeframe. Use closed candles and a held-out or walk-forward sample; record every variant tried.
  • Include spread, fees, slippage, borrow or funding, partial fills, and latency. Reject the setup when net expectancy is not positive or depends on one narrow parameter.
  • Return observed inputs, missing data, cost assumptions, entry, invalidation, exit, and a valid, watch, or no-trade status.
  • Research basis: Liu, Tsyvinski & Wu documented size and momentum factors in crypto returns; this supports relative-strength testing, not fixed BTC-dominance cutoffs or static allocations.

Key Rules

  • NEVER backtest with a present-day survivor list or rank on information unavailable at the rebalance timestamp
  • NEVER treat BTC dominance thresholds as universal cycle boundaries
  • Size from the portfolio risk budget, liquidity, and correlation; do not copy fixed allocation percentages
  • Require a defensive exit for BTC stress, liquidity loss, delisting, or correlation convergence

Related Skills

  • on-chain-analysis -- on-chain metrics confirm accumulation/distribution phases
  • dca-strategy -- DCA into BTC/ETH during accumulation phases

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.