verification-before-completion

Verify quality audit, packaging, and delivery claims with artifact evidence.

32|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/woodfishhhh/EZ_math_model --skill verification-before-completion-woodfishhhh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/woodfishhhh/EZ_math_model/tree/main/skills/ez-math-model/tools/verification-before-completion
Command: npx skills add https://github.com/woodfishhhh/EZ_math_model --skill verification-before-completion-woodfishhhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents an EZ Math Model run from falsely claiming quality_audit, packaging, or final delivery is complete without verifiable evidence.

Core Features & Use Cases

  • Evidence-based pass/fail: Requires every “pass” item in quality_report and export_audit to be backed by concrete artifacts instead of opinion.
  • Multi-type verification: Checks file existence/size, command exit codes and outputs, grep/diff/hash matches, figure-to-reference consistency, numeric consistency, and manifest/zip staging alignment.
  • DOCX/PDF integrity checks: Validates DOCX internals (word/media, m:oMath, w:tbl object counts) and confirms PDF fallback/high-fidelity handling.
  • Use Case: Before delivering the final paper package, verify that all tables/figures referenced in paper.md exist as generated assets and that the exported DOCX/PDF contain the expected objects and counts.

Quick Start

Use verification-before-completion right before the pipeline marks quality_audit, packaging, or final delivery complete, so every claimed result is backed by auditable evidence.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I verify document packaging and quality audit claims with concrete evidence?

Verify packaging and quality audit claims by checking file existence, command exit codes, grep/diff/hash matches, and DOCX object counts to back every pass item with auditable artifacts.

What is evidence-based reporting for final delivery verification?

Evidence-based reporting requires every complete or pass assertion in a quality report to be substantiated by concrete artifacts like command outputs, file sizes, and hash matches rather than opinion.

How do I check DOCX and PDF integrity before final delivery?

Check DOCX integrity by validating internal object counts for word, media, m:oMath, and w:tbl elements, and confirm PDF fallback fidelity to ensure exported files contain expected objects.

How do I validate figure and table references in a math modeling paper package?

Validate figure and table references by confirming all assets referenced in paper.md exist as generated files and matching them against exported DOCX and PDF contents for numeric consistency.

When should I run artifact verification in a math modeling workflow?

Run artifact verification right before the pipeline marks quality audit, packaging, or final delivery complete, ensuring every claimed result is backed by auditable evidence like exit codes and manifest alignment.