manifoldbt-backtester
Runs a declarative strategy spec over OHLCV bars with the manifoldbt Rust engine, pairs the fill log into round trips, and emits the eight inputs the backtest-expert skill scores
Install / Use
npx skills add tradermonty/claude-trading-skills --skill manifoldbt-backtesterInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of manifoldbt-backtester
manifoldbt-backtester scores 91/100 on our quality scale, 1050th of 4,700 Development & Engineering skills we index (top 23%).
Its SKILL.md is 6.1 KB long, well organised into 13 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 2,885 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so manifoldbt-backtester is actively maintained.
- Our last check on 2026-10-29 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
manifoldbt-backtester compared with similar skills
All 4 of these similar skills score higher than manifoldbt-backtester; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| manifoldbt-backtester (this skill)by tradermonty | 91 | 2.9k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install manifoldbt-backtester?
- Run
npx skills add tradermonty/claude-trading-skills --skill manifoldbt-backtester. The install tabs above show the steps for each supported agent. - Which AI agents does manifoldbt-backtester work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is manifoldbt-backtester safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is manifoldbt-backtester still maintained?
- The repository was last updated about 2 months ago, so manifoldbt-backtester is actively maintained.
Skill content
View source on GitHubname: manifoldbt-backtester description: Runs a declarative strategy spec over OHLCV bars with the manifoldbt Rust engine, pairs the fill log into round trips, and emits the eight inputs the backtest-expert skill scores. Use when the user wants to execute a backtest, measure a rule they have described, obtain win rate / average win / average loss / max drawdown from real bars, or feed backtest-expert with measured numbers instead of estimates.
manifoldbt Backtester Skill
Purpose
Execute what backtest-expert teaches. That skill grades a backtest on five
dimensions, and its prerequisites say "metrics are user-provided": it scores
numbers it never produces. This skill produces them. It runs a strategy over
real bars and returns the eight inputs its evaluator asks for.
The two chain in one direction: spec, run, evaluate.
When to Use This Skill
- A user describes a rule and wants it measured
backtest-expertis about to run and the numbers do not exist yet- A win rate, average winner, average loser or drawdown must come from bars
- A strategy's parameter count must be established for scoring
Leave the verdict to backtest-expert. It owns the thresholds and the red
flags, and this skill does not duplicate them.
Prerequisites
- Python 3.9+
pip install manifoldbt(Apache 2.0 with Commons Clause; the free tier covers everything this skill does)- OHLCV bars as CSV or Parquet with columns
timestamp, open, high, low, close, volume - No API key required
Workflow
1. Write the strategy spec
A spec names indicators and one entry condition. Keep it to the smallest rule that states the hypothesis. Every added knob makes an in-sample fit easier to reach by accident, and the evaluator penalises the count.
{
"name": "sma_cross_costed",
"indicators": {
"fast": { "type": "sma", "period": 20 },
"slow": { "type": "sma", "period": 60 }
},
"entry": { "left": "fast", "op": ">", "right": "slow" },
"size": 1.0,
"stop_loss_pct": 1.5,
"fees_bps": 5.0,
"slippage_bps": 2.0
}
Field reference: references/strategy_spec.md.
Set fees_bps and slippage_bps to realistic values before you read any
result. A frictionless run scores 0 on execution realism, and over short holding
periods costs decide whether an edge survives.
2. Run it
python3 scripts/run_backtest.py \
--spec strategy.json \
--data bars.csv \
--symbol BTCUSDT \
--json-out result.json
The script validates the spec before it touches the data, so you see a spec mistake in a second instead of after a long load.
3. Read the warnings before the numbers
The run prints warnings that change how you should read the result: a sample under 30 trades, a span under a year, no friction modelled, or a gap between the engine's win rate and the paired one. Each one is a reason to fix the setup and run again.
Three conditions stop the handoff instead of producing a score: no completed round trips, missing or non-finite maximum drawdown, and scratch trades. The evaluator has no scratch input, so passing a population that contains them would make its derived expectancy disagree with the completed trades.
4. Hand off to backtest-expert
The run ends with a command you can paste. Run it, or invoke the
backtest-expert skill with the same figures:
python3 skills/backtest-expert/scripts/evaluate_backtest.py \
--total-trades 3854 --win-rate 20.24 \
--avg-win-pct 0.2917 --avg-loss-pct 0.2342 \
--max-drawdown-pct 99.2893 --years-tested 0 \
--num-parameters 3 --slippage-tested
Four conversions that fail without an error
Between an engine's output and the evaluator's inputs sit four conversions. Each one yields a plausible number and scores the strategy wrongly. None of them raises.
A fill is one execution, a round trip is two. The raw trade count runs at about twice the number of round trips. Feed fills to the sample-size dimension and you double the apparent sample, which can lift a thin backtest over a threshold it should not clear.
Buy and sell alternate only in the simplest case. That holds for a single-symbol long-only strategy that never scales a position. Shorting breaks it, because a sell can open. Scaling breaks it, because one exit answers several entries. A universe breaks it, because fills interleave. This skill tracks position per symbol and closes a trip when it crosses back through flat. Entry and exit quantities and cash values accumulate across that whole lifecycle; their weighted-average prices are display values, while PnL comes from the cash flows themselves.
Costs decide small trades. At 7 bps a side, a trade that gains 0.1% on price
loses money. Expectancy comes from the win rate and the average winner together,
so a gross win rate beside net averages misstates the edge. Percentages here are
net of fees, and gross_return_pct sits alongside for inspection.
The engine signs drawdown negative. The evaluator wants a positive magnitude. Pass the raw value and a 38% fall scores as a flawless run.
Scope
Supported: sma, ema, rsi over any OHLC column; one entry condition using
>, <, >=, <= against another indicator, a price column or a number;
optional stop-loss and take-profit; fees and slippage in basis points;
long-only.
Refused: multi-condition entries, shorting, multi-asset universes, and indicators outside the three above. The engine does all of these. This skill covers the shapes a one-sentence hypothesis produces, and rejects the rest instead of half-handling it.
Reference Files
references/strategy_spec.mdcovers every spec field, its default, and what validation refusesreferences/metric_bridge.mdcovers the eight inputs, how each is derived, and the trap in each conversion
Scripts
scripts/run_backtest.pyruns a spec against barsscripts/spec.pyvalidates a spec and counts its parametersscripts/round_trips.pypairs fills into round trips with net returnsscripts/bridge.pyassembles the evaluator's eight inputs
spec.py, round_trips.py and bridge.py carry no dependencies and import
without the engine, so you can test the logic without running a backtest.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
