Communitygithub.com

austin-starks/公共投资组合挑战赛

端到端执行公共投资组合挑战赛剧集或附录运行手册的唯一入口点,将每个阶段委托给功能技能。当被要求运行/执行/重放第10集、其比拼赛或其附录(已连接NexusTrade MCP)时使用。读取目标运行手册,固定其真实工件(ID、当前标杆),编排各个阶段,并在有门控的部署处停止。它负责编排;功能技能负责执行。

公共投资组合挑战赛 是什么?

该技能是公共投资组合挑战赛的编排入口点,负责端到端执行指定剧集(如第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 <episode>[ <attempt>]

示例:/run-episode 10 · /run-episode 10 addendum · "run the episode-10 bakeoff"。

首先:加载实际的运行手册(它是本次运行的真相来源)

读取目标运行手册并将其视为该任务+工件的权威来源(该技能只编码顺序和委托):

剧集运行手册形式
10episode-10/BAKEOFF_RUNBOOK.md多家族比拼赛(搜索→认证→锁箱→部署)
10 / addendumepisode-10/addendum/RUNBOOK.md重新设计进出场,证明卖出行为并保留当前标杆优势

在执行任何操作之前,从运行手册中固定:SUBJECT(实盘投资组合/构建)ID、当前标杆(认证研究ID及每折数据)、固定宇宙+资本,以及任何继承的工件。如果运行手册自身的阶段列表与下面的通用顺序不一致,则以运行手册为准。

书挡规则(每集固定)

  • 阶段A首先 — 通过FIELD(get_portfolio → conditionFieldAudit)确认SUBJECT,重新验证当前标杆,抽查一次新鲜的回测,以及(如果是实盘)检查待处理订单 + automaticOrderApproval。提供一段之前状态的描述。
  • 部署最后,且带门控 — 在人类说出该集明确的启动短语("deploy + clean up")之前,不进行克隆、不进行调和、不下达订单。请参阅deploy-gate。
  • 错误是每个阶段的可交付成果 — 任何失败都遵循bug-protocol;隔离受污染的结果。
  • 验证,而非断言 — 每个引擎行为声明都要对照事件/字段/重现(通过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现场验证首先执行;部署最后带门控)。
  • 每个阶段都通过拥有其检查的技能运行,因此裁决是整体的OOS,广度固定在**$25k**,结构性变更强制进行重新扫描,并且每个参数都带有出处。
  • 空结果也是有效结果 — 编排器不会通过扭曲变体来制造胜利。

如果目标运行手册添加、重命名或重新排序阶段,则遵循运行手册——该技能是默认框架,而非覆盖。

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.

相关技能