Communitygithub.com

austin-starks/Public-Portfolio-Challenge

執行公開投資組合挑戰(Public Portfolio Challenge)情節或附錄操作手冊的單一入口點,將各階段委派給功能性技能。當要求執行/重播第10集、其競賽或附錄,並連接 NexusTrade MCP 時使用。

Public-Portfolio-Challenge 是什麼?

這個技能作為公開投資組合挑戰的**編排器入口點**,負責端到端地執行指定情節(如第10集)或附錄的操作手冊。它並未重新實作各階段的具體規範(這些由功能性技能處理),而是按照正確順序讀取、固定實際工件(如投資組合ID、現任基準),並將每個階段委派給對應的技能。技能保證「書擋規則」絕不被跳過:階段A(現場驗證現狀)永遠在最前面,部署永遠被閘控,需等待人類明確的「部署+清理」指令。對於第10集競賽,技能依序執行引擎健全性檢查、保管箱保留測試、策略競賽與部署閘控;對於附錄,則在重新設計進出場機制後停止於部署閘控前。此外,所有引擎行為的主張都會根據事件、欄位或重現驗證,失敗時啟動錯誤協議,並接受無效結果為有效輸出。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/austin-starks/Public-Portfolio-Challenge/tree/HEAD/skills/run-episode

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

執行情節

公開投資組合挑戰的編排器入口點。每個情節都是一項針對特定真實工件的特定工作,但規範是相同的,並存在於功能性技能中。此技能選擇正確的操作手冊,固定其工件,並按順序執行各階段,將每個階段委派給擁有它的技能。它不會重新實作規範——而是將其排序。

調用

/run-episode <情節>[ <嘗試>]

範例:/run-episode 10 · /run-episode 10 addendum ·「執行 episode-10 bakeoff」。

首先:載入實際的操作手冊(它是本次執行的唯一真相來源)

讀取目標操作手冊,並將其視為工作和工件的權威來源(此技能僅編碼排序和委派):

情節操作手冊形狀
10episode-10/BAKEOFF_RUNBOOK.md多家族競賽(搜尋→認證→保管箱→部署)
10 / addendumepisode-10/addendum/RUNBOOK.md重新設計進出場機制,證明賣出行為並保持現任優勢

在執行任何操作之前,從操作手冊中固定:主體(即時投資組合/構建)ID、現任基準(認證研究 ID 及每個折疊的數值)、固定市場與資本,以及任何繼承的工件。操作手冊自身的階段清單若與下方的通用排序不一致,則以操作手冊為準。

書擋規則(每個情節固定)

  • 階段A優先 — 透過 FIELD 確認主體(get_portfolio → conditionFieldAudit),重新驗證現任基準,抽查一個全新回測,並(若為即時)檢查待處理訂單 + automaticOrderApproval。提供一段之前狀態的摘要。
  • 部署最後,且受閘控 — 直到人類說出該情節的明確執行口令(「部署 + 清理」)之前,不得進行克隆、調和或下單。請參閱deploy-gate。
  • 錯誤是每個階段的可交付成果 — 任何失敗都遵循錯誤協議;隔離受污染的結果。
  • 驗證,不要斷言 — 每個引擎行為的主張都必須根據事件/欄位/重現(透過portfolio-certification的第一原則)進行檢查,然後才能記錄到日誌中。

第10集 — 競賽序列

按順序委派:

  1. engine-sanity — S0 合約檢查。發生任何失敗時停止。(這些不計入認證主體。)
  2. lockbox-holdout — 載入 A/B/C 基準作為樣本外(OOS)標準(S1);執行 S1.5 閘控一致性自動放寬。
  3. strategy-bakeoff — 搜尋→認證漏斗:≥3 個家族,每個家族的帳本,判決完整性。每個晉級的種子都通過walk-forward-oos + breadth-audit 認證,並遵守options-structure-rules(硬性閘控)和sweep-reoptimization(從乾淨種子重新掃描)。
  4. lockbox-holdout — 對凍結的決賽者進行單次觸碰保管箱確認(S2)。
  5. deploy-gate — 受閘控。透過 fetch_portfolios 發現即時目標,業主確認,克隆,場地驗證,重新附加監控。

第10集附錄 — 進出場重新設計

附錄遵循相同的認證主幹,但中間部分經過重新設計:

  1. 階段A 基線 + 庫存(上述書擋規則)。
  2. 進出場重新設計: 當前引擎編寫/掃描庫存 → 配對的進出場機制家族 → 事件級別出場綁定審計 → 對晉級設計進行sweep-reoptimization → 與新鮮對照組進行固定配置的walk-forward-oos。
  3. options-structure-rules 硬性閘控 + 對每個決賽者進行breadth-audit 閘控。
  4. 展示,然後停止 — 判決在前,每個折疊的 OOS 表格,與現任者並排比較,出處標籤,誠實的警告,錯誤帳本。不部署。
  5. deploy-gate — 在明確的執行口令下受閘控,僅針對指定的決賽者。

此技能保證的事項

  • 書擋絕不被跳過(階段A現場驗證優先;部署閘控在最後)。
  • 每個階段都透過擁有其檢查的技能執行,因此判決是整體樣本外,廣度為固定 25,000 美元,結構性變更會強制重新掃描,並且每個參數都帶有出處。
  • 無效結果是有效輸出 — 編排器不會為了製造勝利而拷打變體。

如果目標操作手冊新增、重新命名或重新排序階段,請遵循操作手冊——此技能是預設主幹,而非覆蓋。

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

austin-starks/Public-Portfolio-Challenge

Build alternative-data custom indicators on NexusTrade (Reddit/WSB mentions, congressional disclosures, insider filings, news-flow) and wire them into a certified book as a rank/tilt/filter signal. Use when adding alt-data to a strategy, building a CustomIndicator via compute sessions, auditing lookahead safety or per-ticker coverage, or deciding whether a data series is dense enough to drive a rank. Covers the compute-session workflow, the sparse-series rule, and source recipes (see references/). Invoke with the NexusTrade MCP connected.

austin-starks/Public-Portfolio-Challenge

Measure a NexusTrade options book's TRUE participation at a fixed cold-start capital base, defeating the compounded-NAV breadth illusion. Use whenever a book's headline \"holds N/21 names\" needs validating, when a live book collapses to a single name (the OSCR trap), when checking whether a SelectTop / per-name-allocation / total-budget change degraded simultaneous participation, or when a certification needs a breadth gate. Uses audit_backtest_breadth at held-fixed $25k.

austin-starks/Public-Portfolio-Challenge

The \"loudly declare\" protocol for platform, engine, or data bugs during a NexusTrade certification campaign — bugs are a first-class deliverable, not something to route around. Use whenever a NexusTrade tool errors, hangs, or returns numbers that contradict the config; whenever you're tempted to write \"probably an engine quirk\"; or when a discovered bug invalidates prior backtests and results must be quarantined. Includes the bug hand-off doc template (see references/BUG_TEMPLATE.md).

austin-starks/Public-Portfolio-Challenge

The GATED deploy + cleanup flow for a NexusTrade live book — clone the finalist, preview a delta reconcile, stage UNAPPROVED orders, verify fills. Use ONLY after the human explicitly says \"deploy + clean up\" and names a finalist. Covers the clone-before-reconcile ordering, the single-tick reconcile expectation, stale-pending-order hygiene, the signal-freshness gate, and why you can never approve orders yourself. Nothing here runs during certification.

austin-starks/Public-Portfolio-Challenge

The mandatory pre-flight contract checks (Stage S0) that must pass before trusting NexusTrade's certification engine for any strategy work. Use at the start of a bakeoff or certification campaign to prove the walk-forward engine runs end-to-end, windows don't leak, fold winners persist, and the engine doesn't fabricate values for dead/not-yet-listed names. Each check has a STOP-and-report failure mode; these runs do NOT count toward any certification minimum.

austin-starks/Public-Portfolio-Challenge

The single-touch lockbox — a final anti-overfitting holdout run once, after design freeze, on a window held out from every fold, sweep, and search. Use when finalizing a bakeoff winner before deploy, setting up the A/B/C baselines as OOS bars, or running the S1.5 gate-coherence auto-relax. Covers why looking at the lockbox twice burns it, the lockbox pass conditions, and the three baselines. The lockbox is distinct from the walk-forward OOS folds.

austin-starks/Public-Portfolio-Challenge

The hard structural constraints for the Public Portfolio Challenge momentum-LEAP options book — the spread-shape rule, the take-profit convexity-cap footgun, the affordability ladder, and the known losers not to re-test. Use whenever building or auditing an options strategy structure, checking spread-shape compliance before a certification, choosing DTE/strike rungs, or deciding whether a proposed structure change is even allowed. A violation is an automatic certification FAIL.

austin-starks/Public-Portfolio-Challenge

Orchestrate an out-of-sample certification of a NexusTrade trading strategy or live book — the master discipline behind the Public Portfolio Challenge. Use whenever you must decide PASS/FAIL on whether a portfolio holds up out of sample before deploying real money, replaying the Episode 10 runbooks, or running a \"certify my book\" / \"prove it out of sample\" / \"re-certify the fix\" task with the NexusTrade MCP connected. Pulls in walk-forward-oos, breadth-audit, sweep-reoptimization, options-structure-rules, bug-protocol, and deploy-gate.

austin-starks/Public-Portfolio-Challenge

Run a multi-family strategy bakeoff — the SEARCH→CERTIFY funnel that screens many candidate mechanisms down to a certified deploy winner without letting the cheap search layer issue a verdict. Use when replaying the Episode 10 bakeoff, when exploring several distinct strategy families before certifying, when deciding whether \"no deployable winner\" is even a legal conclusion, or when building the per-family certification ledger. Enforces verdict-integrity: only certification can end a campaign.

austin-starks/Public-Portfolio-Challenge

Re-optimize a NexusTrade strategy with a walk-forward SWEEP and label parameter provenance — the discipline that prevents deploying inherited knobs. Use whenever a structural change (sizing, rung depth, universe membership, DTE family, adding a rank signal) forces a re-sweep, when authoring gene_intents from get_sweep_surface, when choosing sweep over GA for a deploy cert, or when selecting the cross-fold-robust winner instead of the per-fold argmax. Invoke with the NexusTrade MCP connected.

austin-starks/Public-Portfolio-Challenge

Run and read a NexusTrade walk-forward out-of-sample study — the certification engine behind the Public Portfolio Challenge. Use when certifying a fixed portfolio (backtest_only) or re-optimizing one (sweep), when setting fold_count / anchored / validation / embargo params, when monitoring a run_walk_forward_study to completion, when reading per-fold OOS returns/Sortino/drawdown, or when a variant's fold calendar needs calendar-alignment against a base control. Invoke with the NexusTrade MCP connected.

相關技能