agent-instructions
Use when writing project instructions for a coding agent (CLAUDE.md, AGENTS.md, or equivalent). Covers what belongs in them, what does not, structure, and…
Use when testing a trading strategy on historical data. Covers the biases that make a backtest lie, realistic costs, walk-forward validation, and the statistics that distinguish an edge from a coincidence.
$ npx -y skills add nimadorostkar/Claude-Skills-collection --skill backtesting --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/backtestingContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when testing a trading strategy on historical data. Covers the biases that make a backtest lie, realistic costs, walk-forward validation, and the statistics that distinguish an edge from a coincidence.
name: backtesting description: Use when testing a trading strategy on historical data. Covers the biases that make a backtest lie, realistic costs, walk-forward validation, and the statistics that distinguish an edge from a coincidence. metadata: category: finance version: 1.0.0 tags: [backtesting, validation, overfitting, bias, statistics]
Test a strategy honestly. The default outcome of a backtest is a beautiful equity curve that describes the past and predicts nothing — and every bias in the process pushes in that direction.
1. **Eliminate the biases before you run anything** — Survivorship (delisted names must be in the universe), look-ahead (data must be used only when it was available), and selection (the strategy must be specified before it is tested). 2. **Model the costs honestly** — Commission, the bid-ask spread, slippage that scales with size and inversely with liquidity, and borrow costs on shorts. Most published edges are smaller than realistic costs. 3. **Split the data before you look at it** — In-sample for development, out-of-sample for validation, and a final hold-out you touch exactly once. 4. **Walk forward** — Re-fit on a rolling window and test on the period immediately after. A single in-sample fit tells you nothing about a strategy that will be run forward in time. 5. **Correct for multiple testing** — If you tested forty variants, the best one looks good by chance. A p-value that has not been adjusted for the number of things you tried is not a p-value. 6. **Stress it** — Perturb the parameters. A strategy that only works with a 14-day lookback and fails with 13 or 15 is fitted to noise.
**A backtest that does not lie to itself:**
def backtest(strategy: Strategy, start: date, end: date) -> BacktestResult:
equity, trades = [], []
for day in trading_days(start, end):
# Point-in-time universe: includes everything that was tradable THAT DAY,
# including companies that were later delisted or went to zero.
universe = universe_as_of(day)
# Point-in-time fundamentals: as reported, on or before this date. Not
# as later restated, and never before the filing date.
data = fundamentals_as_of(day, universe)
# Signals are computed on data available at the CLOSE of the prior day.
# Trades execute at the NEXT day's open. Using today's close to decide
# and today's close to fill is the classic look-ahead error.
signals = strategy.signals(data.shift(1))
for signal in signals:
fill = next_open(signal.symbol, day)
cost = transaction_cost(
price=fill,
shares=signal.shares,
adv=data.loc[signal.symbol, "adv_20d"],
)
trades.append(Trade(day, signal.symbol, fill, cost))
equity.append(mark_to_market(day))
return BacktestResult(equity=equity, trades=trades)
def transaction_cost(price: float, shares: int, adv: float) -> float:
"""Commission + half the spread + slippage that scales with participation."""
notional = price * shares
commission = max(1.0, shares * 0.005)
spread_cost = notional * 0.0005 # half-spread, liquid names
# Market impact grows with the fraction of daily volume you consume.
participation = (shares * price) / max(adv, 1)
impact = notional * 0.10 * math.sqrt(participation) # square-root impact model
return commission + spread_cost + impact**The result, reported honestly:**
Strategy: momentum + quality, 25 names, monthly rebalance.
In-sample Out-of-sample Difference
2010-2018 2019-2024
CAGR (gross) 18.4% 11.2%
CAGR (net of costs) 14.1% 6.8% <- costs take 4-5 points
Sharpe (net) 1.12 0.54 <- halved out of sample
Max drawdown -22.4% -31.7%
Longest drawdown 8 months 19 months <- the number that matters
MultipleA curated library of 137 production-grade skills for Claude and other AI coding agents. Every skill follows one structure, speaks with one voice, and earns its place by changing what the agent does.
Repo: nimadorostkar/Claude-Skills-collection
Use when writing project instructions for a coding agent (CLAUDE.md, AGENTS.md, or equivalent). Covers what belongs in them, what does not, structure, and…
Use when an agent needs state that survives a session or a context compaction. Covers what to persist, file-based memory, structuring notes for retrieval, and…
Use when automating agent behavior with lifecycle hooks. Covers hook events, deterministic enforcement of rules the model should not be trusted to remember,…
Use when packaging skills, commands, hooks, and MCP servers into a distributable plugin. Covers manifest structure, bundling, versioning, testing, and…
Use when writing a new skill for an AI agent. Covers scoping, description writing for reliable triggering, progressive disclosure, and the difference between a…
Use when reviewing or improving an existing agent skill. Covers triggering accuracy, content quality, redundancy with the base model, and measuring whether the…