MileniumTick/edge-pipeline-orchestrator
skills/edge-pipeline-orchestrator/SKILL.md
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.
devops
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add MileniumTick/skills edge-pipeline-orchestratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 12:57 PM7.4s6 files scanned
SKILL.md
- name:
- 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
MileniumTick/rust-engineer
development
VerifiedTrustedCommunity
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
SKILL.mdUpdated Apr 28, 2026
MileniumTick/rust-best-practices
development
VerifiedTrustedCommunity
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
SKILL.mdUpdated Apr 28, 2026
MileniumTick/rust-async-patterns
development
VerifiedTrustedCommunity
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
SKILL.mdUpdated Apr 28, 2026
MileniumTick/revops
tools
VerifiedTrustedCommunity
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.
SKILL.mdUpdated Apr 28, 2026