edge-candidate-agent

Convert daily market observations into edge research tickets and Phase I strategy specs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts daily market observations into reproducible edge research tickets and Phase I-compatible strategy specs.

Core Features & Use Cases

  • Converts daily observations into structured edge research tickets with provenance.
  • Exports Phase I-compatible strategy.yaml and metadata.json for trade-strategy-pipeline handoff.
  • Supports a split workflow with hints, ticket creation, and interface preflight checks.

Quick Start

Run the edge-candidate-agent auto-detect on your EOD data and export the first candidate to the pipeline folder.

Frequently Asked Questions about edge-candidate-agent

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

FAQPage Schema
How do I convert market observations into reproducible edge research tickets?

You can convert daily market observations into structured edge research tickets by running an automation pipeline agent that applies provenance tracking and exports validated artifacts for backtesting.

What is an edge candidate in market analysis automation?

An edge candidate in market analysis is a structured strategy specification generated from daily observations, designed for reproducible backtesting and seamless handoff to a trade-strategy-pipeline.

Do I need Python and PyYAML to generate strategy.yaml files for backtesting pipelines?

Yes, generating strategy.yaml and metadata.json files for pipeline handoff requires Python 3.9+ and PyYAML, along with access to the trade-strategy-pipeline for schema validation.

Can I export Phase I-compatible strategy specs from daily EOD market data?

Yes, you can export Phase I-compatible strategy.yaml and metadata.json specs from EOD market data by processing observations through interface preflight checks and validating them against the trade-strategy-pipeline schema.

What is the best way to automate the creation of strategy specs for pipeline handoff?

The best way to automate strategy spec creation is using a split workflow that processes market observations, generates structured edge research tickets, and runs preflight checks before exporting artifacts to the pipeline folder.

Why does my edge research ticket fail pipeline schema validation?

Edge research tickets fail schema validation when the exported strategy.yaml and metadata.json files lack proper provenance or do not meet Phase I-compatible specifications required by the trade-strategy-pipeline.