edge-strategy-reviewer

Review strategy draft YAML files for edge plausibility and overfitting risk.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/pasie15/claude-trading-skills-marketplace --skill edge-strategy-reviewer-pasie15
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edge-strategy-reviewer
Source: https://github.com/pasie15/claude-trading-skills-marketplace/tree/main/plugins/trading-strategy-tools/skills/edge-strategy-reviewer
Command: npx skills add https://github.com/pasie15/claude-trading-skills-marketplace --skill edge-strategy-reviewer-pasie15

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a deterministic quality gate that automatically evaluates trading strategy drafts for edge plausibility, overfitting risk, sample size adequacy, regime dependency, execution realism, and invalidation quality so only robust candidates are exported from the pipeline.

Core Features & Use Cases

  • Weighted multi-criteria review: Applies eight criteria (C1-C8) with configurable weights to compute a single confidence score and structured findings.
  • Verdict & export gating: Emits PASS / REVISE / REJECT verdicts with confidence scores and export eligibility flags to prevent exporting weak or overfit strategies.
  • Outputs for automation and audit: Produces review.yaml or review.json and optional markdown summaries for pipeline ingestion or human review. Use cases include automated pipeline quality gating after edge-strategy-designer, manual validation before backtesting, and batch triage of candidate drafts.

Quick Start

Review all YAML drafts in reports/edge_strategy_drafts and produce a review.yaml with PASS/REVISE/REJECT verdicts, confidence scores, export eligibility flags, and an optional markdown summary.

Frequently Asked Questions about edge-strategy-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review trading strategy drafts for overfitting risk and edge plausibility?

You can review trading strategy drafts by parsing YAML files and applying eight weighted criteria (C1-C8) to compute an overall confidence score. This process evaluates edge plausibility, overfitting risk, sample size adequacy, and execution realism to emit structured findings.

How does automated quality gating work for backtesting strategy YAML files?

Automated quality gating works by parsing strategy draft YAML files and applying verdict logic to emit PASS, REVISE, or REJECT outcomes. It calculates weighted C1-C8 scores and export eligibility flags to prevent exporting weak or overfit strategies to downstream pipelines.

What is the best way to check if a trading strategy has adequate sample size before exporting?

The best way to check sample size adequacy is to use a multi-criteria review tool that evaluates strategy drafts against eight weighted criteria. It computes a confidence score and generates a review.yaml or review.json file with export eligibility flags.

Does the strategy review process require Python to parse YAML trading drafts?

Yes, the strategy review process requires Python 3.10 or higher with YAML parsing support to read strategy drafts. It processes the YAML files to compute weighted scores and generate review outputs for pipeline ingestion or manual validation.

Can I generate a markdown summary alongside review.yaml for manual strategy validation?

Yes, you can optionally produce a markdown summary alongside review.yaml or review.json outputs. These files contain PASS, REVISE, or REJECT verdicts, confidence scores, and structured findings for both automated pipeline quality gating and human review.

Why should I use a quality gate instead of manually validating trading strategy drafts?

A quality gate provides a deterministic evaluation of edge plausibility, overfitting risk, regime dependency, and invalidation quality. It ensures only robust candidates pass export eligibility checks, reducing human error during manual validation before backtesting.