backtesting-frameworks
Build robust, production-grade backtesting systems that avoid common pitfalls and produce reliable strategy performance estimates.
55
Quality
45%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/backtesting-frameworks/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (backtesting) and emphasizes quality outcomes, but lacks concrete actions and explicit trigger guidance. It reads more like a marketing tagline than a functional skill description that helps Claude choose when to apply it.
Suggestions
Add a 'Use when...' clause with trigger terms like 'backtest', 'trading strategy', 'historical performance', 'strategy simulation'
List specific concrete actions such as 'simulate historical trades', 'calculate performance metrics', 'detect lookahead bias', 'generate equity curves'
Include file types or contexts like 'OHLCV data', 'price history', '.csv market data' to improve trigger matching
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (backtesting systems) and mentions some qualities (robust, production-grade, avoid pitfalls, reliable estimates), but doesn't list concrete actions like 'simulate trades', 'calculate Sharpe ratios', or 'generate equity curves'. | 2 / 3 |
Completeness | Describes what it does (build backtesting systems) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'backtesting' which is a relevant keyword, but misses common variations users might say like 'backtest', 'strategy testing', 'historical simulation', 'trading strategy', or 'performance analysis'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Backtesting systems' is fairly specific to quantitative finance/trading, but could overlap with general trading skills, financial analysis skills, or simulation tools without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, with appropriate progressive disclosure to external resources. However, it severely lacks actionability - the instructions read as a high-level checklist rather than executable guidance. Without concrete code examples, specific commands, or detailed implementation patterns in the main skill file, Claude would struggle to actually implement a backtesting system.
Suggestions
Add at least one concrete, executable code example showing a minimal backtesting loop or event-driven simulation structure
Include specific validation checkpoints in the workflow (e.g., 'Verify no look-ahead bias by checking data timestamps before each signal')
Provide concrete examples of cost models and train/test split implementations rather than just naming the concepts
Add a minimal working example that demonstrates the core pattern before pointing to the detailed playbook
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of concepts Claude already knows. Each bullet point is direct and assumes competence in trading/backtesting concepts. | 3 / 3 |
Actionability | The instructions are vague and abstract with no concrete code, commands, or executable examples. Phrases like 'Build point-in-time data pipelines' and 'Implement event-driven simulation' describe rather than instruct. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence but lack validation checkpoints, specific commands, or feedback loops. There's no guidance on how to verify each step succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | Clear overview structure with well-signaled one-level-deep reference to the implementation playbook. The skill appropriately keeps the main file concise while pointing to detailed resources. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.