agentleFS
JerryLiu369JerryLiu369/awesome-quant-skills/skills/backtesting-audit/vectorbt-backtest/SKILL.md

vectorbt-backtest

Skill3 starsChanged 32 days agoMITView on GitHub

Create a complete VectorBT backtest script for the user. Parse $ARGUMENTS as: strategy symbol exchange interval If no arguments, ask the user which strategy they want.

  • Reads credentials

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 6 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a complete VectorBT backtest script for the user.

    line 14
  2. Distinctive:

    If no arguments, ask the user which strategy they want.

    line 25
  3. Distinctive:

    Read the vectorbt-expert skill rules for reference patterns

    line 29
  4. Very specific:

    Create backtesting/{strategy_name}/ directory if it doesn't exist (on-demand)

    line 30
  5. Very specific:

    Create a .py file in backtesting/{strategy_name}/ named {symbol}_{strategy}_backtest.py

    line 31
  6. Very specific:

    Use the matching template from rules/assets/{strategy}/backtest.py as the starting point

    line 32
  7. Very specific:

    If user provides a DuckDB path, load data directly via duckdb.connect(path, read_only=True) instead of OpenAlgo API.

    line 36
  8. Very specific:

    If openalgo.ta is not importable (standalone DuckDB), use inline exrem() fallback.

    line 37
  9. Very specific:

    Use ta.exrem() to clean duplicate signals (always .fillna(False) before exrem)

    line 40
  10. Very specific:

    Run vbt.Portfolio.from_signals() with min_size=1, size_granularity=1

    line 41
  11. Distinctive:

    Never use icons/emojis in code or logger output

    line 50
  12. Very specific:

    Use fees=0.00018, fixed_fees=20 for F&O futures

    line 54
  13. Very specific:

    Default: NIFTY 50 via OpenAlgo (symbol="NIFTY", exchange="NSE_INDEX")

    line 73
  14. Distinctive:

    If user specifies a different benchmark, use that instead

    line 74
  15. Distinctive:

    Always compare: Total Return, Sharpe, Sortino, Max Drawdown

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
<!-- Imported from: https://github.com/marketcalls/vectorbt-backtesting-skills Source Path: .claude/skills/backtest/SKILL.md Curated for awesome-quant-skills -->

name: backtest description: Quick backtest a strategy on a symbol. Creates a complete .py script with data fetch, signals, backtest, stats, and plots. argument-hint: "[strategy] [symbol] [exchange] [interval]" allowed-tools: Read, Write, Edit, Bash, Glob, Grep

Create a complete VectorBT backtest script for the user.

Arguments

Parse $ARGUMENTS as: strategy symbol exchange interval

  • $0 = strategy name (e.g., ema-crossover, rsi, donchian, supertrend, macd, sda2, momentum)
  • $1 = symbol (e.g., SBIN, RELIANCE, NIFTY). Default: SBIN
  • $2 = exchange (e.g., NSE, NFO). Default: NSE
  • $3 = interval (e.g., D, 1h, 5m). Default: D

If no arguments, ask the user which strategy they want.

Instructions

  1. Read the vectorbt-expert skill rules for reference patterns
  2. Create backtesting/{strategy_name}/ directory if it doesn't exist (on-demand)
  3. Create a .py file in backtesting/{strategy_name}/ named {symbol}_{strategy}_backtest.py
  4. Use the matching template from rules/assets/{strategy}/backtest.py as the starting point
  5. The script must:
    • Load .env from the project root using find_dotenv() (walks up from script dir automatically)
    • Fetch data via client.history() from OpenAlgo
    • If user provides a DuckDB path, load data directly via duckdb.connect(path, read_only=True) instead of OpenAlgo API. Auto-detect format: Historify (market_data table, epoch timestamps) vs custom (ohlcv table, date+time). See vectorbt-expert rules/duckdb-data.md.
    • If openalgo.ta is not importable (standalone DuckDB), use inline exrem() fallback.
    • Use OpenAlgo ta for ALL indicators by default (EMA, SMA, RSI, MACD, BBands, ATR, ADX, STDDEV, MOM, and 90+ more) - from openalgo import ta
    • Only use TA-Lib if the user explicitly says "talib"/"TA-Lib" in their request; specialty indicators (Supertrend, Donchian, Ichimoku, HMA, KAMA, ALMA, ZLEMA, VWMA) always come from OpenAlgo ta regardless, since TA-Lib has no equivalent
    • Use ta.exrem() to clean duplicate signals (always .fillna(False) before exrem)
    • Run vbt.Portfolio.from_signals() with min_size=1, size_granularity=1
    • Indian delivery fees: fees=0.00111, fixed_fees=20 for delivery equity
    • Fetch NIFTY benchmark via OpenAlgo (symbol="NIFTY", exchange="NSE_INDEX")
    • Print full pf.stats()
    • Print Strategy vs Benchmark comparison table (Total Return, Sharpe, Sortino, Max DD, Win Rate, Trades, Profit Factor)
    • Explain the backtest report in plain language for normal traders
    • Generate the OpenStatz interactive dashboard tearsheet via ostz.dashboard(...) if openstatz is available - a self-contained offline HTML file, no server needed (always use OpenStatz, never QuantStats; never the legacy ostz.reports.html static report). Set strategy_returns.name (e.g. "EMA 20/50 Crossover - SBIN") and benchmark.name before calling dashboard() - that name, not the title= argument, is what the tearsheet shows as the strategy header/column/legend (see the openstatz-tearsheet rule)
    • Plot equity curve + drawdown using Plotly (template="plotly_dark")
    • Export trades to CSV
  6. Never use icons/emojis in code or logger output
  7. For futures symbols (NIFTY, BANKNIFTY), use lot-size-aware sizing:
    • NIFTY: min_size=65, size_granularity=65 (effective 31 Dec 2025)
    • BANKNIFTY: min_size=30, size_granularity=30
    • Use fees=0.00018, fixed_fees=20 for F&O futures

Available Strategies

StrategyKeywordTemplate
EMA Crossoverema-crossoverassets/ema_crossover/backtest.py
RSIrsiassets/rsi/backtest.py
Donchian Channeldonchianassets/donchian/backtest.py
Supertrendsupertrendassets/supertrend/backtest.py
MACD Breakoutmacdassets/macd/backtest.py
SDA2sda2assets/sda2/backtest.py
Momentummomentumassets/momentum/backtest.py
Dual Momentumdual-momentumassets/dual_momentum/backtest.py
Buy & Holdbuy-holdassets/buy_hold/backtest.py
RSI Accumulationrsi-accumulationassets/rsi_accumulation/backtest.py

Benchmark Rules

  • Default: NIFTY 50 via OpenAlgo (symbol="NIFTY", exchange="NSE_INDEX")
  • If user specifies a different benchmark, use that instead
  • For yfinance: use ^NSEI for India, ^GSPC (S&P 500) for US markets
  • Always compare: Total Return, Sharpe, Sortino, Max Drawdown

Example Usage

/backtest ema-crossover RELIANCE NSE D /backtest rsi SBIN /backtest supertrend NIFTY NFO 5m

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.