backtest

Test trading strategies on historical data with Monte Carlo simulation

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/backtest/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, highly actionable API reference with executable TypeScript across all major features, but it inlines the full reference rather than splitting it into referenced files and lacks an explicit sequenced workflow with validation checkpoints.

Suggestions

Move the bulk of the TypeScript API reference into a separate REFERENCE.md and keep SKILL.md as a concise overview pointing to it, improving progressive disclosure.

Add an explicit end-to-end workflow (configure -> run -> validate results -> walk-forward -> Monte Carlo) with checkpoints for sanity-checking outputs before relying on metrics.

Trim the 'Metrics Explained' table and inline config comments where the values duplicate knowledge Claude already has, or relocate them to the reference file.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code examples and tables with little padding, but includes minor over-explanation Claude largely already knows (the 'Metrics Explained' good-value thresholds and inline config comments).	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript covering the common cases (engine creation, basic run, walk-forward, Monte Carlo, metrics, custom strategy) with concrete parameters and outputs.	5 / 5
Workflow Clarity	Sections roughly imply a flow (create engine -> run -> walk-forward -> Monte Carlo -> metrics) but there is no explicit sequenced workflow and no validation checkpoints, fitting the 'sequence present but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	Good section headers organize the content, but the entire API reference is inlined in SKILL.md with no one-level-deep references to separate reference files, fitting 'content that should be separate is inline'.	3 / 5
	Total	15 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 concisely states a clear, niche capability with two concrete actions, but it omits any 'Use when...' trigger guidance and lacks common synonyms like 'backtest' that users would naturally say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to backtest or validate a trading strategy, run Monte Carlo simulations, or analyze strategy performance on historical data.'

Include natural synonyms and the term 'backtest'/'backtesting' in the description so it matches how users actually phrase the request.

Mention walk-forward analysis or performance metrics to broaden specificity beyond the two current actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('trading strategies') and two concrete actions ('Test...on historical data' and 'Monte Carlo simulation'), but coverage is not comprehensive given the body also covers walk-forward, custom strategies, and metrics.	3 / 5
Completeness	Clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Contains relevant phrases ('trading strategies', 'historical data', 'Monte Carlo simulation') but misses common natural variations users would say such as 'backtest', 'backtesting', or 'paper trading'.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (trading strategy backtesting) with low conflict risk, though it could mildly overlap with general finance or data-analysis skills and lacks explicit distinct trigger phrases.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/backtest/SKILL.md
Commit: 715fd4a

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.