What problem does it solve? Research projects that mandate Wasserstein-2 as the primary persistence-diagram metric often accumulate inconsistent W₁, unsubscripted W, or ambiguous W_p references across manuscript drafts and code. This Skill audits both sources and produces a structured reconciliation report so notation violations are found before they block publication milestones. ## Core Features & Use Cases - Manuscript Scanning: Flags W₁ usage, unsubscripted W, bottleneck-only metrics, and ambiguous Wasserstein references in Markdown drafts under papers/. - Code Scanning: Detects Python Wasserstein calls missing an explicit p=2 or order=2 argument, including gudhi, persim, and giotto-tda library calls. - Structured Report: Cross-references findings against the canonical notation standard and outputs a reconciliation table with suggested fixes, without modifying anything automatically. - Use Case: Before submitting a topology paper, run the audit across all manuscripts and domain packages to confirm every Wasserstein reference complies with the W₂ convention and receive a blocking/non-blocking status for Phase 0. ## Quick Start Ask the assistant to run a Wasserstein audit across all papers and code to list every W₁ or ambiguous Wasserstein usage with suggested fixes.
