backtest-diagnose

Diagnose failed or underperforming backtests, locate the root cause, and fix the issue

Quality

73%

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 ./agent/src/skills/backtest-diagnose/SKILL.md

Quality

Content

81%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 content is highly actionable with an explicit, validated diagnostic workflow and bounded repair loop. It is well-organized and concise, with only minor verbosity in the evidence-handling section.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with dense, well-organized tables and checklists, though the "Evidence hookup" paragraph is somewhat verbose and could be trimmed.	4 / 5
Actionability	Concrete commands (pip install, AST parse check), specific file paths, and a copy-paste-ready AST validation command dominate; a few taxonomy fixes remain high-level hints like "Add length checks".	4 / 5
Workflow Clarity	A clear 5-step diagnostic sequence is paired with explicit validation checkpoints (hard-gate checklist, AST syntax pass, rerun backtest) and a bounded 3-iteration feedback loop.	5 / 5
Progressive Disclosure	The single SKILL.md is well-structured with clear section headers and one clearly signaled cross-skill reference; no bundle files exist, so all content is appropriately inline with minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

66%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 is concise, third-person, and names concrete actions within a clear backtest niche. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness.

Suggestions

Add a "Use when..." clause, e.g. "Use when a backtest fails, raises an error, or produces poor or unexpected results."

Include a few natural synonyms users might say, such as "strategy" or "trading simulation", to broaden trigger coverage.

Tighten the three verbs so they are distinct rather than overlapping ("diagnose" and "locate the root cause" are near-synonymous).

Dimension	Reasoning	Score
Specificity	Names the backtest domain plus three concrete actions — "Diagnose failed or underperforming backtests", "locate the root cause", and "fix the issue" — with only minor gaps in coverage.	4 / 5
Completeness	It clearly answers what the skill does but omits any "Use when..." trigger clause, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural terms a user would say ("backtest", "failed", "underperforming") are present, but synonyms like "strategy results" or "trading simulation" are missing.	4 / 5
Distinctiveness Conflict Risk	The "backtest" niche is clear and distinct, though there is minor overlap risk with adjacent trading or strategy skills.	4 / 5
	Total	15 / 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: HKUDS/Vibe-Trading
Path: agent/src/skills/backtest-diagnose/SKILL.md
Commit: d71ed8d

Reviewed: 3 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.