Communitygithub.com

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.

What is Public-Portfolio-Challenge?

Public-Portfolio-Challenge is a Claude Code agent skill that 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.

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

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Run Episode

The orchestrator entry point for the Public Portfolio Challenge. Every episode is a specific job over specific real artifacts, but the discipline is the same and lives in the functional skills. This skill picks the right runbook, pins its artifacts, and runs the stages in order, delegating each to the skill that owns it. It does not re-implement the discipline — it sequences it.

Invocation

/run-episode <episode>[ <attempt>]

Examples: /run-episode 10 · /run-episode 10 addendum · "run the episode-10 bakeoff".

First: load the actual runbook (it is the source of truth for THIS run)

Read the target runbook and treat it as authoritative for the job + artifacts (this skill only encodes the ordering and delegation):

EpisodeRunbookShape
10episode-10/BAKEOFF_RUNBOOK.mdMulti-family bakeoff (search→certify→lockbox→deploy)
10 / addendumepisode-10/addendum/RUNBOOK.mdRedesign entries + exits, prove sell behavior and retain the incumbent edge

From the runbook, pin before doing anything: the SUBJECT (live book / build) IDs, the incumbent bar (cert study id + per-fold numbers), the fixed universe + capital, and any carried-over artifacts. The runbook's own Stage list wins if it disagrees with the generic ordering below.

The bookend rules (fixed for every episode)

  • Stage A first — confirm the SUBJECT by FIELD (get_portfolio → conditionFieldAudit), re-verify the incumbent bar, spot-check one fresh backtest, and (if live) check pending orders + automaticOrderApproval. Deliver a one-paragraph before state.
  • Deploy last, and GATED — no clone, no reconcile, no orders until the human says the episode's explicit go phrase ("deploy + clean up"). See deploy-gate.
  • Bugs are a deliverable at every stage — bug-protocol on any failure; quarantine tainted results.
  • Verify, don't assert — every engine-behavior claim checked against events/fields/repro (via portfolio-certification's first principles) before it lands in the log.

Episode 10 — the bakeoff sequence

Delegates, in order:

  1. engine-sanity — S0 contract checks. STOP on any failure. (These don't count toward the cert body.)
  2. lockbox-holdout — load A/B/C baselines as OOS bars (S1); run the S1.5 gate-coherence auto-relax.
  3. strategy-bakeoff — the SEARCH→CERTIFY funnel: ≥3 families, per-family ledger, verdict-integrity. Each promoted seed is certified through walk-forward-oos + breadth-audit, held to options-structure-rules (hard gates) and sweep-reoptimization (re-sweep from a clean seed).
  4. lockbox-holdout — the single-touch lockbox confirmation on the frozen finalist (S2).
  5. deploy-gate — GATED. Discover the live target via fetch_portfolios, owner-confirm, clone, field-verify, re-attach monitoring.

Episode 10 addendum — entry and exit redesign

The addendum follows the same certification spine with a redesigned middle:

  1. Stage A baseline + inventory (bookend rule above).
  2. Entry + exit redesign: current-engine authoring/sweep inventory → matched entry/exit mechanism families → event-level exit-binding audit → sweep-reoptimization on the promoted design → fixed-config walk-forward-oos vs a fresh control.
  3. options-structure-rules hard-gate + breadth-audit gate on every finalist.
  4. Present, then stop — verdict up top, per-fold OOS table, side-by-side vs incumbent, provenance labels, honest caveats, bug ledger. No deploy.
  5. deploy-gate — GATED on the explicit go, for the named finalist only.

What this skill guarantees

  • The bookends are never skipped (Stage-A field-verify first; deploy gated last).
  • Each stage runs through the skill that owns its checks, so the verdict is holistic OOS, breadth is at fixed $25k, structural changes force a re-sweep, and every parameter carries provenance.
  • A null result is a valid outcome — the orchestrator does not torture variants to manufacture a win.

If the target runbook adds, renames, or reorders stages, follow the runbook — this skill is the default spine, not an override.

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.

Related Skills