Validate Topological Results

VerifiedSafe

Check mathematical correctness of TDA results against known benchmarks and internal consistency checks.

Sby Skills Guide Bot
Data & AIAdvanced
7/30/2026
Claude CodeCursorWindsurf
#topological-data-analysis#tda-validation#persistence-diagrams#reproducibility

Recommended for

Automated summary

Validates topological data analysis results by checking persistence diagrams, total persistence scaling, null model consistency, and cross-era replication against known benchmarks.

Strengths

  • Comprehensive checklist covering diagram sanity, scaling, null models, and Wasserstein metrics.
  • Provides known benchmarks from published studies for reproducibility.
  • Catches subtle inconsistencies in TDA pipelines.

Limitations

  • Requires pre-computed TDA results in specific JSON format.
  • Only validates against provided benchmarks; not a full TDA framework.
  • Assumes fixed parameters (e.g., landmark count L) from the referenced study.
When to use it

Use after running a TDA pipeline to automatically verify that outputs meet expected mathematical and statistical properties.

When not to use it

Do not use for exploratory TDA without reference benchmarks, or when results are from non-standard methods not covered by the validation rules.

Security analysis

Safe
Quality score90/100

The skill is a static validation checklist with no executable commands, destructive actions, or data exfiltration instructions. It poses no security risk.

No concerns found

How this analysis is made

Examples

Validate a TDA result file
/validate-topology trajectory_tda results/trajectory_tda_integration/04_nulls_wasserstein.json
Check persistence diagram sanity
Run /validate-topology on my persistence results to verify that birth values are non-negative and death values exceed birth.
Benchmark comparison
Use /validate-topology to compare my BHPS order-shuffle H0 p-value against the known benchmark from the P01 study.

/validate-topology — Validate Topological Results

Check mathematical correctness of TDA results against known benchmarks and internal consistency checks.

Usage

/validate-topology [domain] [result-file]

Example: /validate-topology trajectory_tda results/trajectory_tda_integration/04_nulls_wasserstein.json


Validation checklist

Persistence diagram sanity

  • [ ] All birth values ≥ 0
  • [ ] All death values > birth (finite features)
  • [ ] H₀ has exactly one infinite feature (the final connected component)
  • [ ] Feature counts are plausible for landmark count L: H₀ has L-1 finite features; H₁ count varies

Total persistence scaling

  • [ ] Total persistence scales approximately linearly with L (±15% across a 2× range)
  • [ ] Maximum persistence is stable across L values (should vary < 5%)

Null model consistency

  • [ ] Label/cohort shuffle p-values are non-significant (negative control)
  • [ ] Markov-2 null generates more total persistence than Markov-1 (higher-order Markov → more structured surrogates)
  • [ ] Null distribution standard deviations are plausible (not near-zero, not huge)

Wasserstein-specific

  • [ ] W(obs↔null) and W(null↔null) are of comparable magnitude (within ~3×)
  • [ ] p-value = proportion of null-null distances ≥ mean(obs-null distances)
  • [ ] 500 null-null pairs is sufficient for stable p-value at 3 decimal places

Cross-era replication

  • [ ] BHPS-era order-shuffle H₀ p-value ≈ USoc order-shuffle direction (both significant or both not)
  • [ ] BHPS-era Markov-1 direction ≈ USoc (both non-significant under total persistence)

Known benchmarks (trajectory_tda / P01)

| Test | Expected | Source | |---|---|---| | USoc order-shuffle H₀ (total persistence, L=5000) | p < 0.005 | P01 v5 Table 2 | | USoc Markov-1 H₀ (total persistence) | p = 1.000 | P01 v5 Table 2 | | USoc Markov-1 H₀ (Wasserstein, L=2000) | p = 0.002 | P01 v5 Table 2b | | BHPS order-shuffle H₀ | p = 0.000 | P01 v5 §4.7 | | BHPS Markov-1 H₀ | p = 1.000 | P01 v5 §4.7 | | GMM bootstrap ARI | 0.646 ± 0.086 | P01 v5 §3.5 |

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/validate-topological-results-ms71b45w/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/validate-topological-results-ms71b45w' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/validate-topological-results-ms71b45w/download' --output '.skill-downloads/validate-topological-results-ms71b45w/SKILL.md.part' && mv '.skill-downloads/validate-topological-results-ms71b45w/SKILL.md.part' '.skill-downloads/validate-topological-results-ms71b45w/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/validate-topological-results-ms71b45w/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills