verify-and-archive

Automates post-run verification and archival of completed FRESCO production runs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/j-mckerracher/agent-research --skill verify-and-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-and-archive
Source: https://github.com/j-mckerracher/agent-research/tree/main/skills-main/verify-and-archive
Command: npx skills add https://github.com/j-mckerracher/agent-research --skill verify-and-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a pipeline completes, this skill verifies output integrity and archives artifacts to the depot, reducing manual post-run tasks.

Core Features & Use Cases

  • Post-run verification checks: schema conformance, dtype stability, required columns, and timestamp parseability.
  • Archival automation: copies manifests, validation results, logs, and config to a persistent depot.
  • Reproducibility support: ensures run metadata and records are stored for future citation.

Quick Start

Run the verify-and-archive workflow immediately after a completed run to verify outputs and copy artifacts to the depot.

Frequently Asked Questions about verify-and-archive

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

FAQPage Schema
How do I verify pipeline output integrity after a production run completes?

Yes, you can automate artifact archival by copying manifests, validation results, logs, and config files to a persistent depot, ensuring run metadata and records are stored for future citation and reproducibility.

Can I automate artifact archival for multiple production runs at once?

Yes, you can automate artifact archival by copying manifests, validation results, logs, and config files to a persistent depot, ensuring run metadata and records are stored for future citation and reproducibility.

What does post-run verification check in a data pipeline output?

Post-run verification is needed after a pipeline completes to validate output integrity automatically, reducing manual post-run tasks and ensuring only schema-conforming, timestamp-parseable artifacts are archived to the depot.

When do I need to run post-run verification on completed pipeline outputs?

Post-run verification is needed after a pipeline completes to validate output integrity automatically, reducing manual post-run tasks and ensuring only schema-conforming, timestamp-parseable artifacts are archived to the depot.

Does post-run verification support reproducibility for archived pipeline runs?

Yes, post-run verification supports reproducibility by ensuring run metadata and records are stored alongside archived artifacts, allowing future citation and validation of completed production runs.