backtesting-frameworks
Build robust, production-grade backtesting systems that avoid common pitfalls and produce reliable strategy performance estimates.
Works with
--- name: backtesting-frameworks description: Build robust, production-grade backtesting systems that avoid common pitfalls and produce reliable strategy performance estimates. license: MIT --- # Backtesting Frameworks Build robust, production-grade backtesting systems that avoid common pitfalls and produce reliable strategy performance estimates. ## Use this skill when - Developing trading strategy backtests - Building backtesting infrastructure - Validating strategy performance and robustness - Avoiding common backtesting biases - Implementing walk-forward analysis ## Do not use this skill when - You need live trading execution or investment advice - Historical data quality is unknown or incomplete - The task is only a quick performance summary ## Instructions - Define hypothesis, universe, timeframe, and evaluation criteria. - Build point-in-time data pipelines and realistic cost models. - Implement event-driven simulation and execution logic. - Use train/validation/test splits and walk-forward testing. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Safety - Do not present backtests as guarantees of future performance. - Avoid providing financial or investment advice. ## Resources - `resources/implementation-playbook.md` for detailed patterns and examples. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

