edge-pipeline-orchestrator
Orchestrate the full edge research pipeline from candidate detection through strategy design, review, revision, and export
Install / Use
npx skills add tradermonty/claude-trading-skills --skill edge-pipeline-orchestratorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of edge-pipeline-orchestrator
edge-pipeline-orchestrator scores 90/100 on our quality scale, 1203rd of 2,780 Automation skills we index (top 44%).
Its SKILL.md is 4.2 KB long, well organised into 13 sections with 4 code examples: a solid amount of guidance for an agent.
With 2,885 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so edge-pipeline-orchestrator is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
edge-pipeline-orchestrator compared with similar skills
All 4 of these similar skills score higher than edge-pipeline-orchestrator; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| edge-pipeline-orchestrator (this skill)by tradermonty | 90 | 2.9k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install edge-pipeline-orchestrator?
- Run
npx skills add tradermonty/claude-trading-skills --skill edge-pipeline-orchestrator. The install tabs above show the steps for each supported agent. - Which AI agents does edge-pipeline-orchestrator work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is edge-pipeline-orchestrator safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is edge-pipeline-orchestrator still maintained?
- The repository was last updated about 2 months ago, so edge-pipeline-orchestrator is actively maintained.
Skill content
View source on GitHubname: edge-pipeline-orchestrator description: Orchestrate the full edge research pipeline from candidate detection through strategy design, review, revision, and export. Use when coordinating multi-stage edge research workflows end-to-end.
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
- Load pipeline configuration from CLI arguments
- Run auto_detect stage if --from-ohlcv is provided (generates tickets from raw OHLCV data)
- Run hints stage to extract edge hints from market summary and anomalies
- Run concepts stage to synthesize abstract edge concepts from tickets and hints
- Run drafts stage to design strategy drafts from concepts
- 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
- Export eligible drafts (PASS + export_ready_v1 + exportable entry_family)
- 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:
- Run auto_detect to produce
market_summary.json+anomalies.json - Claude Code analyzes data and generates edge hints
- 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
- Run orchestrator with
--llm-ideas-fileand--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 architecturereferences/revision_loop_rules.md— Review-revision feedback loop rules and heuristics
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
