paper-build-output-hygiene

Validate and clean AutoLabOS-generated TeX/PDF paper bundles for artifact integrity.

5|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/lhy0718/AutoLabOS --skill paper-build-output-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paper-build-output-hygiene
Source: https://github.com/lhy0718/AutoLabOS/tree/main/.codex/skills/paper-build-output-hygiene
Command: npx skills add https://github.com/lhy0718/AutoLabOS --skill paper-build-output-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AutoLabOS often produces TeX/PDF/paper bundles that must be validated and cleaned to keep operator-facing outputs coherent and trustworthy.

Core Features & Use Cases

  • Ensure canonical paper artifact bundle generation and validation across builds.
  • Detect and remove duplicate or unnecessary bundles; verify page-budget and wiring of output paths.
  • Use case: operators can rapidly confirm that the test outputs align with the canonical bundle before release.

Quick Start

Run the hygiene check against the current AutoLabOS paper bundle to verify structure and identify fixes.

Frequently Asked Questions about paper-build-output-hygiene

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

FAQPage Schema
How do I validate AutoLabOS paper bundle structure and fix missing artifacts?

Run a hygiene check against the current AutoLabOS paper bundle to verify its structure. The process analyzes the bundle to identify missing artifacts and outputs actionable changes to align with canonical requirements.

What is canonical paper artifact bundle generation and why is it needed?

Canonical paper artifact bundle generation ensures TeX/PDF outputs are structurally valid and correctly wired. It is needed to keep operator-facing paper builds coherent, trustworthy, and free of duplicate or unnecessary files before release.

How do I remove duplicate TeX/PDF bundles and verify page-budget compliance?

Automated cleanup removes duplicate or unnecessary bundles from the output directory. The validation process simultaneously checks page-budget compliance and verifies correct wiring of canonical output paths across test runs.

Can I use this to check TeX/PDF status across multiple test runs?

Yes, the validation process specifically verifies TeX/PDF status and checks the wiring of canonical output paths across test runs to ensure end-to-end paper builds maintain artifact integrity before release.

What are the limitations of automated paper artifact cleanup for AutoLabOS builds?

The automated cleanup focuses strictly on validating structure, removing duplicates, and checking page-budget compliance. It requires an existing AutoLabOS-generated TeX/PDF bundle to analyze and does not generate new paper artifacts from scratch.