Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
tradermonty avatar

Edge Candidate Agent

  • 925 installs
  • 2.6k repo stars
  • Updated August 4, 2026
  • tradermonty/claude-trading-skills

edge-candidate-agent is a Claude Code skill that converts US equity market observations and anomalies into prioritized research tickets and Phase I pipeline candidate files for developers running systematic trading resea

About

edge-candidate-agent is a trading research skill that transforms end-of-day US equity observations into reproducible research tickets and Phase I-compatible candidate specifications for the trade-strategy-pipeline. It generates and ranks long-side edge ideas, then exports strategy.yaml and metadata.json when ideas are validated, with preflight checks against the edge-finder-candidate/v1 interface before backtests run. Developers use it when hypotheses or anomalies must become structured pipeline inputs rather than ad hoc notes. Signal quality and schema compatibility are prioritized over aggressive strategy promotion.

  • Converts EOD observations and hypotheses into reproducible research tickets
  • Exports validated candidates as strategy.yaml + metadata.json for trade-strategy-pipeline Phase I
  • Performs preflight interface compatibility checks for edge-finder-candidate/v1
  • Supports both standalone end-to-end runs and split workflow export/validation
  • Prioritizes signal quality and schema compatibility over volume of strategies

Edge Candidate Agent by the numbers

  • 925 all-time installs (skills.sh)
  • +81 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #1,190 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/tradermonty/claude-trading-skills --skill edge-candidate-agent

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs925
repo stars2.6k
Last updatedAugust 4, 2026
Repositorytradermonty/claude-trading-skills

How do you turn market hypotheses into strategy pipeline tickets?

Turn daily market observations, anomalies, and hypotheses into structured, pipeline-ready equity research tickets and candidate strategy files.

Who is it for?

Quant developers running US equity long-side research who feed trade-strategy-pipeline Phase I with structured candidate specs.

Skip if: Discretionary traders avoiding YAML pipelines, crypto-only workflows, or teams without the trade-strategy-pipeline tooling.

When should I use this skill?

User wants to convert market anomalies or hypotheses into research tickets, strategy.yaml exports, or pipeline preflight checks.

What you get

Prioritized research tickets, strategy.yaml candidate specs, metadata.json files, and edge-finder-candidate/v1 compatibility checks.

  • Research tickets
  • strategy.yaml
  • metadata.json

Files

SKILL.mdMarkdownGitHub ↗

Edge Candidate Agent

Overview

Convert daily market observations into reproducible research tickets and Phase I-compatible candidate specs. Prioritize signal quality and interface compatibility over aggressive strategy proliferation. This skill can run end-to-end standalone, but in the split workflow it primarily serves the final export/validation stage.

When to Use

  • Convert market observations, anomalies, or hypotheses into structured research tickets.
  • Run daily auto-detection to discover new edge candidates from EOD OHLCV and optional hints.
  • Export validated tickets as strategy.yaml + metadata.json for trade-strategy-pipeline Phase I.
  • Run preflight compatibility checks for edge-finder-candidate/v1 before pipeline execution.

Prerequisites

  • Python 3.9+ with PyYAML installed.
  • Access to the target trade-strategy-pipeline repository for schema/stage validation.
  • uv available when running pipeline-managed validation via --pipeline-root.

Output

  • strategies/<candidate_id>/strategy.yaml: Phase I-compatible strategy spec.
  • strategies/<candidate_id>/metadata.json: provenance metadata including interface version and ticket context.
  • Validation status from scripts/validate_candidate.py (pass/fail + reasons).
  • Daily detection artifacts:
  • daily_report.md
  • market_summary.json
  • anomalies.json
  • watchlist.csv
  • tickets/exportable/*.yaml
  • tickets/research_only/*.yaml

Position in Split Workflow

Recommended split workflow:

1. skills/edge-hint-extractor: observations/news -> hints.yaml 2. skills/edge-concept-synthesizer: tickets/hints -> edge_concepts.yaml 3. skills/edge-strategy-designer: concepts -> strategy_drafts + exportable ticket YAML 4. skills/edge-candidate-agent (this skill): export + validate for pipeline handoff

Workflow

1. Run auto-detection from EOD OHLCV:

  • skills/edge-candidate-agent/scripts/auto_detect_candidates.py
  • Optional: --hints for human ideation input
  • Optional: --llm-ideas-cmd for external LLM ideation loop

2. Load the contract and mapping references:

  • references/pipeline_if_v1.md
  • references/signal_mapping.md
  • references/research_ticket_schema.md
  • references/ideation_loop.md

3. Build or update a research ticket using references/research_ticket_schema.md. 4. Export candidate artifacts with skills/edge-candidate-agent/scripts/export_candidate.py. 5. Validate interface and Phase I constraints with skills/edge-candidate-agent/scripts/validate_candidate.py. 6. Hand off candidate directory to trade-strategy-pipeline and run dry-run first.

Quick Commands

Daily auto-detection (with optional export/validation):

python3 skills/edge-candidate-agent/scripts/auto_detect_candidates.py \
  --ohlcv /path/to/ohlcv.parquet \
  --output-dir reports/edge_candidate_auto \
  --top-n 10 \
  --hints path/to/hints.yaml \
  --export-strategies-dir /path/to/trade-strategy-pipeline/strategies \
  --pipeline-root /path/to/trade-strategy-pipeline

Create a candidate directory from a ticket:

python3 skills/edge-candidate-agent/scripts/export_candidate.py \
  --ticket path/to/ticket.yaml \
  --strategies-dir /path/to/trade-strategy-pipeline/strategies

Validate interface contract only:

python3 skills/edge-candidate-agent/scripts/validate_candidate.py \
  --strategy /path/to/trade-strategy-pipeline/strategies/my_candidate_v1/strategy.yaml

Validate both interface contract and pipeline schema/stage rules:

python3 skills/edge-candidate-agent/scripts/validate_candidate.py \
  --strategy /path/to/trade-strategy-pipeline/strategies/my_candidate_v1/strategy.yaml \
  --pipeline-root /path/to/trade-strategy-pipeline \
  --stage phase1

Export Rules

  • Keep validation.method: full_sample.
  • Keep validation.oos_ratio omitted or null.
  • Export only supported entry families for v1:
  • pivot_breakout with vcp_detection
  • gap_up_continuation with gap_up_detection
  • Mark unsupported hypothesis families as research-only in ticket notes, not as export candidates.

Guardrails

  • Reject candidates that violate schema bounds (risk, exits, empty conditions).
  • Reject candidate when folder name and id mismatch.
  • Require deterministic metadata with interface_version: edge-finder-candidate/v1.
  • Use --dry-run in pipeline before full execution.

Resources

skills/edge-candidate-agent/scripts/export_candidate.py

Generate strategies/<candidate_id>/strategy.yaml and metadata.json from a research ticket YAML.

skills/edge-candidate-agent/scripts/validate_candidate.py

Run interface checks and optional StrategySpec/validate_spec checks against trade-strategy-pipeline.

skills/edge-candidate-agent/scripts/auto_detect_candidates.py

Auto-detect edge ideas from EOD OHLCV, generate exportable/research tickets, and optionally export/validate automatically.

references/pipeline_if_v1.md

Condensed integration contract for edge-finder-candidate/v1.

references/signal_mapping.md

Map hypothesis families to currently exportable signal families.

references/research_ticket_schema.md

Ticket schema used by export_candidate.py.

references/ideation_loop.md

Hint schema and external LLM ideation command contract.

Related skills

How it compares

Use edge-candidate-agent for ticket and YAML spec generation; use downstream pipeline skills when candidates are already validated and ready to backtest.

FAQ

What files does edge-candidate-agent produce?

edge-candidate-agent outputs prioritized research tickets and, for validated ideas, Phase I pipeline files including strategy.yaml and metadata.json aligned to the edge-finder-candidate/v1 interface.

When should edge-candidate-agent run in the trading workflow?

edge-candidate-agent runs when daily EOD observations or anomalies must become reproducible tickets and pipeline-ready US equity long-side candidates before trade-strategy-pipeline backtests.

AI & Agent Buildingagentsautomationresearch

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.