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

Edge Pipeline Orchestrator

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

edge-pipeline-orchestrator is a Claude Code skill that runs the full quantitative edge research pipeline from market data through strategy generation, review, revision, and export for developers automating systematic tra

About

edge-pipeline-orchestrator is a workflow skill from tradermonty/claude-trading-skills that chains edge research stages into one automated run. It loads pipeline configuration from CLI arguments, processes tickets or OHLCV inputs, moves through candidate detection, strategy design, review, and revision loops, then exports finalized strategies. Developers can resume partially completed runs from the drafts stage or dry-run to preview outputs without exporting. Reach for edge-pipeline-orchestrator when quant research steps are already scripted separately but need reliable end-to-end coordination with feedback loops instead of manual handoffs between notebooks and scripts.

  • Orchestrates 7-stage edge research pipeline end-to-end
  • Supports full run from tickets or OHLCV data, resume from drafts, and dry-run preview
  • Implements review-revision feedback loop with verdict accumulation (PASS/REJECT/REVISE)
  • Exports only PASS + export_ready_v1 strategies with full pipeline_run_manifest.json trace
  • Max 2 review iterations before downgrading remaining REVISE verdicts to research_probe

Edge Pipeline Orchestrator by the numbers

  • 805 all-time installs (skills.sh)
  • +91 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #1,320 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-pipeline-orchestrator

Add your badge

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

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

How do you orchestrate quant edge research end to end?

Automatically coordinate an entire multi-step quantitative trading research pipeline from raw market data through strategy generation, review, revision, and final expor

Who is it for?

Quant developers with modular edge-research scripts who need one command to run detection, design, review, revision, and export with resume support.

Skip if: Developers placing live orders or teams wanting a single-indicator backtest without multi-stage strategy review and export gates.

When should I use this skill?

User wants to run the full edge pipeline, resume from drafts, dry-run strategy export, or coordinate multi-stage quant research end to end.

What you get

Reviewed strategy drafts, revision history, and exported strategy artifacts from a coordinated pipeline run.

  • exported strategies
  • strategy drafts
  • pipeline run preview

Files

SKILL.mdMarkdownGitHub ↗

Edge Pipeline Orchestrator

Coordinate all edge research stages into a single automated pipeline run.

When to Use

  • Run the full edge pipeline from tickets (or OHLCV) to exported strategies
  • Resume a partially completed pipeline from the drafts stage
  • Review and revise existing strategy drafts with feedback loop
  • Dry-run the pipeline to preview results without exporting

Workflow

1. Load pipeline configuration from CLI arguments 2. Run auto_detect stage if --from-ohlcv is provided (generates tickets from raw OHLCV data) 3. Run hints stage to extract edge hints from market summary and anomalies 4. Run concepts stage to synthesize abstract edge concepts from tickets and hints 5. Run drafts stage to design strategy drafts from concepts 6. Run review-revision feedback loop:

  • Review all drafts (max 2 iterations)
  • PASS verdicts accumulated; REJECT verdicts accumulated
  • REVISE verdicts trigger apply_revisions and re-review
  • Remaining REVISE after max iterations downgraded to research_probe

7. Export eligible drafts (PASS + export_ready_v1 + exportable entry_family) 8. Write pipeline_run_manifest.json with full execution trace

CLI Usage

# Full pipeline from tickets
python3 scripts/orchestrate_edge_pipeline.py \
  --tickets-dir path/to/tickets/ \
  --output-dir reports/edge_pipeline/

# Full pipeline from OHLCV
python3 scripts/orchestrate_edge_pipeline.py \
  --from-ohlcv path/to/ohlcv.csv \
  --output-dir reports/edge_pipeline/

# Resume from drafts stage
python3 scripts/orchestrate_edge_pipeline.py \
  --resume-from drafts \
  --drafts-dir path/to/drafts/ \
  --output-dir reports/edge_pipeline/

# Review-only mode
python3 scripts/orchestrate_edge_pipeline.py \
  --review-only \
  --drafts-dir path/to/drafts/ \
  --output-dir reports/edge_pipeline/

# Dry run (no export)
python3 scripts/orchestrate_edge_pipeline.py \
  --tickets-dir path/to/tickets/ \
  --output-dir reports/edge_pipeline/ \
  --dry-run

Output

All artifacts are written to --output-dir:

output-dir/
├── pipeline_run_manifest.json
├── tickets/          (from auto_detect)
├── hints/hints.yaml  (from hints)
├── concepts/edge_concepts.yaml
├── drafts/*.yaml
├── exportable_tickets/*.yaml
├── reviews_iter_0/*.yaml
├── reviews_iter_1/*.yaml  (if needed)
└── strategies/<candidate_id>/
    ├── strategy.yaml
    └── metadata.json

Claude Code LLM-Augmented Workflow

Run the LLM-augmented pipeline entirely within Claude Code:

1. Run auto_detect to produce market_summary.json + anomalies.json 2. Claude Code analyzes data and generates edge hints 3. Save hints to a YAML file:

- title: Sector rotation into industrials
  observation: Tech underperforming while industrials show relative strength
  symbols: [CAT, DE, GE]
  regime_bias: Neutral
  mechanism_tag: flow
  preferred_entry_family: pivot_breakout
  hypothesis_type: sector_x_stock

4. Run orchestrator with --llm-ideas-file and --promote-hints:

python3 scripts/orchestrate_edge_pipeline.py \
  --tickets-dir path/to/tickets/ \
  --llm-ideas-file llm_hints.yaml \
  --promote-hints \
  --as-of 2026-02-28 \
  --max-synthetic-ratio 1.5 \
  --strict-export \
  --output-dir reports/edge_pipeline/

Optional Flags

  • --as-of YYYY-MM-DD — forwarded to hints stage for date filtering
  • --strict-export — export-eligible drafts with any warn finding get REVISE instead of PASS
  • --max-synthetic-ratio N — cap synthetic tickets to N × real ticket count (floor: 3)
  • --overlap-threshold F — condition overlap threshold for concept deduplication (default: 0.75)
  • --no-dedup — disable concept deduplication

Note: --llm-ideas-file and --promote-hints are effective only during full pipeline runs. --resume-from drafts and --review-only skip hints/concepts stages, so these flags are ignored.

Resources

  • references/pipeline_flow.md — Pipeline stages, data contracts, and architecture
  • references/revision_loop_rules.md — Review-revision feedback loop rules and heuristics

Related skills

How it compares

Use edge-pipeline-orchestrator when multiple edge-research stages already exist and you need orchestration, resume, and dry-run gates rather than a single backtest script.

FAQ

Can edge-pipeline-orchestrator resume a partial run?

edge-pipeline-orchestrator supports resuming from the drafts stage when a prior pipeline run stopped mid-workflow. Load CLI configuration and continue review, revision, and export without restarting candidate detection.

What inputs does edge-pipeline-orchestrator accept?

edge-pipeline-orchestrator runs from tickets or OHLCV market data through candidate detection, strategy design, review, revision, and export. Pipeline behavior is controlled through CLI-loaded configuration.

AI & Agent Buildingagentsautomationresearch

This week in AI coding

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

unsubscribe anytime.