edge-strategy-designer

Convert edge_concepts.yaml into strategy draft YAMLs with risk-profile calibration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transform high-level trading edge concepts into concrete, testable strategy drafts and optional exportable ticket files so hypothesis-driven research can progress to validation and deployment without manual specification work.

Core Features & Use Cases

  • Variant generation: Produce multiple variants per concept (core, conservative, research-probe) with hypothesis-type calibrated exits.
  • Risk-aware defaults: Apply risk_profile selection, hypothesis-specific exit overrides, and clamp reward-to-risk to an RR_FLOOR to reduce review failures.
  • Export readiness: Emit strategy_drafts YAML, a run_manifest, and optional exportable ticket YAMLs compatible with downstream export_candidate tooling for pipeline validation and ingestion.

Quick Start

Generate balanced strategy drafts from your edge_concepts.yaml and write outputs to a directory for downstream validation and export.

Frequently Asked Questions about edge-strategy-designer

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

FAQPage Schema
How do I convert edge concepts into strategy drafts for validation?▼

To convert edge concepts into strategy drafts, process your edge_concepts.yaml file to generate structured strategy_drafts YAMLs, applying risk-profile calibration and RR_FLOOR clamping at 1.5 to ensure candidates are export-ready for downstream validation.

What is the best way to generate testable trading strategy variants from YAML?▼

Generating testable trading strategy variants from YAML involves producing multiple drafts per concept, such as core, conservative, and research-probe variants, each calibrated with hypothesis-type specific exit overrides to prepare for pipeline ingestion.

Does this workflow apply RR_FLOOR clamping and risk-profile selection automatically?▼

Yes, this workflow applies RR_FLOOR clamping at 1.5 and risk-profile selection automatically during strategy draft generation, reducing review failures by ensuring reward-to-risk ratios meet minimum thresholds before export.

How do I export strategy drafts as tickets compatible with export_candidate.py?▼

You can export strategy drafts as tickets compatible with export_candidate.py by processing edge_concepts.yaml to emit optional exportable ticket YAMLs alongside a run_manifest, enabling seamless downstream pipeline validation and ingestion.

What inputs do I need to generate strategy drafts and run manifests?▼

You need an edge_concepts.yaml file as input to generate strategy drafts and a run manifest, which together provide the structured foundation for variant generation, risk-profile calibration, and export-ready ticket creation.

When do I need optional exportable ticket YAMLs in a trading research workflow?▼

You need optional exportable ticket YAMLs when moving trading research from hypothesis drafting to deployment, as they provide the structured format required by downstream export_candidate.py tooling for pipeline validation and ingestion.