Communitygithub.com

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

运行多策略族擂台赛——SEARCH→CERTIFY漏斗,从大量候选机制中筛选出经认证的可部署优胜者,同时禁止廉价搜索层做出最终裁决。适用于复盘第10集擂台赛、探索多个不同策略族后进行认证、判断“无可部署优胜者”是否是合法结论,或为每个策略族构建认证分类账时使用。强制执行裁决完整性:只有认证才能结束活动。

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

本技能(Multi-Family Strategy Bakeoff)实现了一个严格的两层漏斗结构:首先是**SEARCH(搜索)层**(低成本),负责使用回测、创建变体、优化和系统扫描等工具对策略族进行初步筛选,但**严禁**在该层做出任何最终裁决(如PASS/FAIL或“无可部署优胜者”)。只有通过**CERTIFY(认证)层**的滚动前扫(walk-forward sweep)验证,才能产生最终结论。该技能强制要求至少对**3个截然不同的机制族**进行认证(不能是同一族的三个微调变体),且每个族最多允许3次认证尝试。此外,为了确保裁决的完整性,任何声称“结构不可行”的结论必须基于系统扫描+三族认证证据,并明确指出每个族失败的具体 gate,否则该活动被视为无效。技能还提供了详细的认证分类账表模板,以及每族认证的具体流程,包括参与率、名称多样性、验证收益等硬性门槛。该技能适用于Claude Code、Cursor等支持自定义工具链的AI Agent平台,通过定义严格的工具使用顺序和裁决权限来防止AI过早或错误地做出投资组合决策。

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

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

多策略族擂台赛

一个双层 SEARCH → CERTIFY 漏斗,附带强制的最低工作量要求。核心规则: 严禁在搜索层做出任何裁决。 只有滚动前扫认证(walk-forward-oos) 才能结束活动。

两个工具,两份职责

  • SEARCH 层(低成本):backtest_portfolio、create_portfolio_variant、optimize_portfolio、 systematic_sweep。它只能 淘汰或提升 一个想法进入认证阶段。输出“一组排好序的种子” 并且严禁做出最终裁决。
  • CERTIFY 层(重活):对提升的种子进行滚动前扫认证。只有该层 可以得出通过/失败或“无可部署优胜者”的结论。

在宣称某个邻域无效之前,必须在搜索层对 部署 × 结构 × DTE × delta 网格执行 systematic_sweep,这是强制性的。

强制的最低工作量

  • 至少认证 ≥ 3 个不同的机制族 才能给出任何“无优胜者”裁决。必须是真正不同的 机制,而不是同一族的三种微调。族菜单(任选 ≥3):(a) 动量长期看涨/垂直价差; (b) 状态切换长期/中性; (c) 定义信用 / 空头溢价(在横盘/下跌行情中获利);(d) 日历 / 对角时间价差; (e) 保护性领口或看跌价差融资的多头头寸。
  • 每个族最多 3 次认证尝试(从干净的种子重新扫描,使用改进的 gene_intents、更密集的网格或更宽的验证范围),之后该族便“耗尽”。
  • 实际工作量:约 3–9 次扫描认证,外加已认证的当前种子作为基准。
  • 每次扫描不可简化:至少 ≥3 个 gene_intents 轴 × 各自 ≥3 个值(参见 扫描重优化 了解 确切的字段映射)。1轴或2值的扫描不算合格。

按族认证分类账(必需)

将此表格记录在运行日志中——没有分类账行的族表示未被探索过:

| 族名 | 种子ID | get_sweep_surface ✓ | gene_intents 轴数 | 研究ID | crossFoldRobustSelection 键 | 已组装账簿ID | 每折OOS门限结果 | 提升/淘汰(原因) |

每种子认证循环

get_sweep_surface → run_walk_forward_study(先使用 preview_only)→ 读取 aggregate.crossFoldRobustSelection → 组装部署形状的账簿 → 对组装后的对象进行门限判断 → 写入分类账行。认证门槛(certification:true):参与率 ≥ 0.35、 不同名称数 ≥ 9、验证收益 ≥ 0、验证索提诺比率 ≥ 0.5。

裁决完整性规则(活动核心纪律)

  • 零项优化认证 = 无效,而非“诚实的无部署”。 在未对候选种子运行优化认证的情况下做出任何裁决—— 尤其是“无可部署优胜者”/“结构不可行”——将导致活动无效。(之前的运行在运行了 零项优化认证后宣称不可行。)
  • 禁止基于 N 个手工构建的点声称不可行——必须引用 systematic_sweep + ≥3族 工作量,并指出每个族失败的单个约束门限,附上研究ID证据。
  • 数据中一个反例即可禁止全面不可行声明——定位具体的约束条件, 不要泛化。
  • 约束门限归因: 每次淘汰必须指出单个失败的门限 + 经认证的证据。 “总体上表现不佳”不是淘汰理由。
  • 每个候选者只做一次机制变更——这样淘汰/提升的归因才能清晰。
  • 补救措施一致性: 提议的补救措施不得与被淘汰候选者的实测状态相矛盾 (不要针对在头寸上限下失败的账簿提议“增加部署”;不要针对因回撤而失败的账簿提议“增加凸性”)。

有关可负担性淘汰路径和已知失败模式的详情,请参见 期权结构规则; 有关基线(A/B/C)和最终单次确认的详情,请参见 锁仓保留集。

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

The single entry point that executes a Public Portfolio Challenge episode or addendum runbook end-to-end, delegating each stage to the functional skills. Use when asked to run/execute/replay Episode 10, its bakeoff, or its addendum with the NexusTrade MCP connected. Reads the target runbook, pins its real artifacts (IDs, the incumbent bar), sequences the stages, and stops at the gated deploy. It orchestrates; the functional skills do the work.

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.

相关技能