result-provenance-review

Validate computational results for reproducibility via file metadata and script outputs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps to confirm that computational results are reproducible, correctly recorded, and trustworthy for downstream use.

Core Features & Use Cases

  • Provenance Assurance: Verifies the reproducibility of results, including caching, seeds, output paths, and no-overwrite behavior.
  • Result Validation: Ensures that results match their recorded parameters and seeds.
  • Use Case: When reviewing or producing TDL computational result files, this skill helps to ensure that results are reliable for further analysis or reporting.

Quick Start

Run the result-provenance-review skill on the latest result file to confirm its reproducibility and accuracy.

Frequently Asked Questions about result-provenance-review

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

FAQPage Schema
How do I validate computational reproducibility for my analysis outputs?

Computational reproducibility validation involves checking result files for date-suffixed filenames, correct seeds, and cache provenance to ensure outputs match recorded parameters and prevent silent overwrites.

What is result provenance tracking in data analysis workflows?

Result provenance tracking is the process of verifying that computational outputs are reproducible by auditing file metadata, script outputs, and adherence to git and vault protocols to guarantee data integrity for downstream use.

How do I prevent silent overwrites when saving computational results?

To prevent silent overwrites, enforce date-suffixed filenames and verify output paths when generating computational results, ensuring previous outputs remain intact and accurately recorded for reproducibility.

Does computational result validation check for correct random seeds and cache provenance?

Yes, computational result validation checks for correct seeds and cache provenance by verifying that outputs match recorded parameters and adhere to established git and vault protocols for trustworthy analysis.

When do I need to review file metadata for result assurance?

Review file metadata for result assurance when producing or evaluating computational result files, ensuring outputs are reliable for reporting, reproducibility, and downstream data integration.