skills/edge-strategy-reviewer/SKILL.md
Critically review strategy drafts from edge-strategy-designer for edge plausibility, overfitting risk, sample size adequacy, and execution realism. Use when strategy_drafts/*.yaml exists and needs quality gate before pipeline export. Outputs PASS/REVISE/REJECT verdicts with confidence scores.
npx skillsauth add MileniumTick/skills edge-strategy-reviewerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Deterministic quality gate for strategy drafts produced by edge-strategy-designer.
edge-strategy-designer generates strategy_drafts/*.yamledge-candidate-agent via the pipelineedge-strategy-designer)--drafts-dir or a single --draft file| # | Criterion | Weight | Key Checks | |---|-----------|--------|------------| | C1 | Edge Plausibility | 20 | Thesis quality, domain terms, mechanism keywords (continuous 50-95) | | C2 | Overfitting Risk | 20 | 5-tier filter count scoring (90/80/60/40/10), precise threshold penalty | | C3 | Sample Adequacy | 15 | Continuous scoring from estimated annual opportunities (10-95) | | C4 | Regime Dependency | 10 | Cross-regime validation | | C5 | Exit Calibration | 10 | Stop-loss, reward-to-risk | | C6 | Risk Concentration | 10 | Position sizing limits | | C7 | Execution Realism | 10 | Volume filter, export consistency | | C8 | Invalidation Quality | 5 | Signal count and specificity |
# Review all drafts in a directory
python3 skills/edge-strategy-reviewer/scripts/review_strategy_drafts.py \
--drafts-dir reports/edge_strategy_drafts/ \
--output-dir reports/
# Single draft review
python3 skills/edge-strategy-reviewer/scripts/review_strategy_drafts.py \
--draft reports/edge_strategy_drafts/draft_xxx.yaml \
--output-dir reports/
# JSON output with markdown summary
python3 skills/edge-strategy-reviewer/scripts/review_strategy_drafts.py \
--drafts-dir reports/edge_strategy_drafts/ \
--output-dir reports/ \
--format json \
--markdown-summary
# Strict export mode: export-eligible drafts with any warn → REVISE
python3 skills/edge-strategy-reviewer/scripts/review_strategy_drafts.py \
--drafts-dir reports/edge_strategy_drafts/ \
--output-dir reports/ \
--strict-export
Primary output: review.yaml (or review.json)
generated_at_utc: "2026-02-28T12:00:00+00:00"
source:
drafts_dir: "/path/to/strategy_drafts"
draft_count: 4
summary:
total: 4
PASS: 1
REVISE: 2
REJECT: 1
export_eligible: 1
reviews:
- draft_id: "draft_xxx_core"
verdict: "PASS"
confidence_score: 80
export_eligible: true
findings: [...]
revision_instructions: []
references/review_criteria.md — Detailed scoring rubric for C1-C8references/overfitting_checklist.md — Overfitting detection heuristicsdevelopment
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.
development
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.
development
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.
tools
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.