What problem does it solve?
validate-publication prevents publication-staging or release repositories from failing APP compliance by systematically detecting missing files, broken paths, incorrect claims, reproduction gaps, and privacy leaks that would block a reader agent from understanding and reproducing the work.
Core Features & Use Cases
- APP factual consistency checks: flags clear mismatches between what AGENTS.md, README, supplementary materials, and skills claim versus what the paper and runnable artifacts actually support.
- Path, structure, and command validity checks: verifies that every referenced file exists, that commands and figure/table reproduction mappings resolve correctly, and that final-validation statuses are not left in temporary states.
- Privacy and confidentiality scanning: searches the entire publication tree (including code, paper sources, configs, and notebooks) for credentials, personal data, internal/private references, and other sensitive information.
- Reader-agent usability and completeness review: confirms cross-file coherence (README vs AGENTS.md vs figure map vs validation evidence) and checks that required smoke-test artifacts exist for final release validation.
Quick Start
Use validate-publication on your publication staging directory by running the skill at full mode to produce a terminal validation report.
