pima-audit

Audit machine learning experiments for data leakage and validate claims against published literature.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill pima-audit-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pima-audit
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/pima-audit
Command: npx skills add https://github.com/yakeworld/Synthos --skill pima-audit-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research papers and benchmarks often report suspiciously high accuracy caused by data leakage, incomplete baselines, or non-reproducible experiments. This Skill audits machine learning experiment directories (such as PIDD diabetes classification studies) to detect leakage, verify baseline completeness, and cross-check published claims against reproducible results. ## Core Features & Use Cases - Cross-Dataset Leakage Auditing: Runs consistent audits across datasets (PIDD, INSCAT, Diabetes 130-US) with fixed ZeroReplacer, pipeline structure, CV settings, and metrics so comparisons remain valid. - Baseline Completeness Checks: Detects gaps between recorded and claimed model counts (e.g., 27 vs 32 baselines) and names missing models such as DummyClassifier or StackingClassifier. - Literature Validation: Searches Semantic Scholar, CrossRef, and PubMed for papers reporting accuracy above 90% or F1 above 0.70, flags data leakage risk, and cross-references OpenML public experiments (PIDD ID:292) as third-party verification. - Use Case: Given a research directory claiming 32 baselines with 95% accuracy on PIDD, the audit reveals only 27 models were run, identifies the 5 missing classifiers, and shows post-leakage F1 converges near 0.70, contradicting the published claim. ## Quick Start Audit this PIDD experiment directory for data leakage, verify the baseline count matches the paper's claims, and cross-check high-accuracy papers in the literature for leakage risk.

Frequently Asked Questions about pima-audit

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

FAQPage Schema
How do I detect data leakage in machine learning experiments?

Run a methodological audit that compares claimed metrics against leakage-corrected baselines under fixed conditions. Post-leakage F1 scores converging near 0.70 are an empirical signal, and papers reporting accuracy above 90% should be flagged for leakage risk.

How to verify a paper's baseline count matches its claims?

Compare the recorded model count in the benchmark against the claimed number, then name each missing model explicitly. For example, a 27 versus 32 discrepancy is resolved by identifying absent classifiers like DummyClassifier, GaussianProcessClassifier, and StackingClassifier, then rerunning.

Can a Jupyter notebook serve as a reproducible experiment record?

No, a notebook whose cells have no outputs is treated only as a design draft and is rejected as a reproducible record. Experiment code must be a standalone .py script with complete outputs to be accepted.

Why is cross-dataset comparison invalid in some audits?

Comparison is invalid when experimental conditions differ across datasets, such as different ZeroReplacer settings, pipeline structures, CV setups, or evaluation metrics. All conditions must be fixed identically before cross-dataset conclusions can be drawn.

What literature sources validate high-accuracy ML paper claims?

Use Semantic Scholar combined with CrossRef or PubMed for multi-source search, since a single API may miss papers. Filter for accuracy above 90% or F1 above 0.70, then cross-reference OpenML public experiments such as PIDD ID:292 for third-party verification.