manuscript-provenance

Verify that a manuscript is a faithful rendering of computational outputs. Every number, table, figure, category label, ordering, and threshold in the document must trace to a specific script, config file, or pipeline output.

Manual data entry in a manuscript is a reproducibility defect.

This skill produces a provenance map — a structured report linking each manuscript artifact to its generating code — and flags every break in the chain.

Computational provenance audit verifying that every number, table, figure, ordering, and terminology in a manuscript is derived from code and scripts — not manually entered. Cross-references LaTeX source against the codebase to detect hardcoded values, stale outputs, broken pipelines, and manual data entry. Companion to manuscript-review: that skill audits the document as prose; this skill audits whether the document is faithfully generated from code. Use when the user says "check provenance", "verify reproducibility", "audit my pipeline", "are my numbers from code", "check manuscript against scripts", "provenance audit", or any request to verify that manuscript content traces back to computational outputs. Source: mathews-tom/praxis-skills.