What problem does it solve? Summarizing a quantitative trading strategy's backtest and rigor-gate results is easy to get wrong: a status="live" field sounds like a rigor endorsement, a bare passes_rigor_gate boolean hides pending states, and phrases like "statistically proven" or "corrects for multiple testing" contradict what the code actually does. This Skill maps every field of the strategy_passports table to its true meaning and enforces honest framing. ## Core Features & Use Cases - Field-by-field reference: Documents every column of StrategyPassportRecord (identity, lifecycle, ownership, backtest metrics, rigor gate results) with source line numbers. - Gate semantics: Explains what passes_rigor_gate and the tri-state rigor_gate_status mean, including that the badge is always graded at the strictest level and that curated strategies are graded at num_trials=1. - Claim integrity rules: Lists five forbidden phrasings (e.g., "statistically proven", "95% confidence") plus five pitch anti-claims that must never appear in strategy summaries. - Use Case: When a user asks "does this strategy pass the rigor gate?", read the passport via GET /api/strategies/passports/{id}, report DSR, PBO, and out-of-sample Sharpe with their exact scope, and explicitly separate status from the gate verdict. ## Quick Start Read the passport for strategy ID X and summarize its rigor gate results honestly, stating whether status is live and whether the gate passed as separate facts.
