wasserstein-audit

Scan manuscript drafts and codebases for W₁ versus W₂ Wasserstein metric inconsistencies.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/stephendor/TDL --skill wasserstein-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wasserstein-audit
Source: https://github.com/stephendor/TDL/tree/main/.agents/skills/wasserstein-audit
Command: npx skills add https://github.com/stephendor/TDL --skill wasserstein-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies inconsistencies between W₁ and W₂ Wasserstein metrics in manuscript drafts and codebases, ensuring adherence to project conventions.

Core Features & Use Cases

  • Consistency Check: Scans manuscript and code for W₁ vs W₂ metric inconsistencies.
  • Verification: Ensures project convention mandates Wasserstein-2 as the primary metric.
  • Use Case: For projects using Wasserstein metrics, this Skill helps catch errors early in the development process.

Quick Start

Run the 'wasserstein-audit' command to scan all manuscript drafts and codebase for inconsistencies.

Frequently Asked Questions about wasserstein-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my manuscript drafts and codebase for W1 and W2 Wasserstein metric inconsistencies?

Wasserstein metric inconsistencies between W1 and W2 occur when manuscript drafts and codebases fail to adhere to the W2 standard. This Skill uses Python scripts to scan files, detecting metric deviations early in the project development workflow.

How do I scan a codebase to verify project convention adherence to the Wasserstein-2 metric?

Scanning a codebase for Wasserstein-2 adherence requires running the 'wasserstein-audit' command. It analyzes project files to verify W2 is the primary metric and flags W1 usage errors within your development workflow.

What is the best way to catch Wasserstein metric usage errors in a research project before publication?

The best way to catch Wasserstein metric usage errors is to run automated consistency checks. This Skill scans manuscript drafts and codebase files to enforce the W2 metric standard, identifying W1 vs W2 inconsistencies early.

Do I need Python scripts to run a Wasserstein consistency check on my manuscript drafts?

You need Python scripts to run this Wasserstein consistency check on manuscript drafts. The Skill utilizes Python scripts to scan and analyze files, detecting W1 and W2 metric deviations when you run the 'wasserstein-audit' command.

Can I use this consistency check for projects that mix W1 and W2 Wasserstein metrics intentionally?

This consistency check targets projects mandating Wasserstein-2 as the primary metric standard. If your project intentionally mixes W1 and W2 metrics, this audit will flag those W1 usages as inconsistencies rather than acceptable variations.