技能 backtesting-frameworks
📊

backtesting-frameworks

安全 🌐 网络访问⚡ 包含脚本⚙️ 外部命令

Build reliable trading backtests

也可从以下获取: sickn33

Trading backtests often hide bias and overstate performance. This skill provides patterns and checks to design trustworthy backtests that handle look-ahead bias, survivorship bias, and transaction costs properly.

支持: Claude Codex Code(CC)
📊 69 充足
1

下载技能 ZIP

2

在 Claude 中上传

前往 设置 → 功能 → 技能 → 上传技能

3

开启并开始使用

测试它

正在使用“backtesting-frameworks”。 How do I avoid survivorship bias in equity backtests?

预期结果:

  • Use point-in-time constituent lists that include delisted securities
  • Obtain historical data providers that maintain delisted symbol data
  • Document the data source and its survivorship handling approach
  • Test your universe against known historical index compositions

正在使用“backtesting-frameworks”。 What are the key metrics to evaluate a backtest?

预期结果:

  • Sharpe ratio for risk-adjusted returns
  • Maximum drawdown for worst-case loss
  • Calmar ratio combining return and drawdown
  • Win rate and profit factor for trading quality

安全审计

安全
v4 • 1/17/2026

This is a pure documentation skill containing only instructional content and Python code examples for building trading backtests. All 46 static findings are false positives. The scanner incorrectly flagged: ASCII diagram delimiters (backticks in markdown), dictionary keys (certificate/key files), financial terms like 'sharpe' (weak crypto), and legitimate function calls (dynamic constructor). No executable code, network calls, file access, credential harvesting, or data exfiltration patterns exist.

2
已扫描文件
838
分析行数
3
发现项
4
审计总数
审计者: claude 查看审计历史 →

质量评分

38
架构
100
可维护性
85
内容
23
社区
100
安全
87
规范符合性

你能构建什么

Validate a new strategy

Apply bias checks and walk-forward splits before trusting performance estimates.

Compare alternatives

Use consistent cost models and metric standards across multiple strategy candidates.

Design backtest engine

Follow event-driven architecture patterns and execution modeling guidance.

试试这些提示

Start a backtest plan
Outline a basic backtesting workflow that avoids look-ahead bias and includes realistic transaction costs.
Choose backtester type
Compare event-driven and vectorized backtesting approaches for a daily equity strategy with 50 symbols.
Set walk-forward splits
Propose walk-forward train and test windows for 10 years of daily data and explain the rationale.
Add robustness checks
List Monte Carlo analyses and metrics to assess drawdown risk for a strategy returns series.

最佳实践

  • Reserve a final test set that is never used for optimization
  • Model commissions and slippage with realistic parameters based on your execution target
  • Report drawdowns and risk-adjusted metrics, not only raw returns

避免

  • Optimizing parameters on the full history without out-of-sample testing
  • Ignoring delisted securities when building equity universes
  • Assuming zero trading costs for high turnover strategies

常见问题

Which AI platforms work with this skill?
This skill is platform agnostic and works with Claude, Codex, and Claude Code for guidance.
What are the limits of this skill?
It provides design guidance and does not run code, fetch market data, or execute trades.
Can I integrate this with my existing backtester?
Yes, use the architectural patterns to review or extend your current implementation.
Does this skill access my data or credentials?
No, it provides guidance only and does not access files, credentials, or external systems.
What if my backtest results look too good?
Recheck for look-ahead bias, survivorship bias, and verify cost assumptions are realistic.
How does this compare to a full backtesting library?
This provides design patterns and best practices, not a complete backtesting library.