About presentation-validation
A validation skill for presentation projects, using a read-only dispatcher to run checks against a specified project folder. It can produce human-readable or structured reports without changing project files.
Key features
- 01Runs generation or proofread validation profiles
- 02Checks media-spec role rules
- 03Supports structured JSON findings
- 04Keeps project files and state unchanged
- 05Provides remediation guidance in reports
Use cases
- 01Validating a presentation project after generation
- 02Checking proofread results
- 03Reviewing media-spec roles before approval
- 04Passing structured findings to another process
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/presentation-validationin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
evals/presentation-validation.jsonscripts/presentation-validationpresentation-validation.mjstests/diagram-checks.test.mjspresentation-validation.test.mjstests/fixtures/marp-export/PRESENTASJON.htmlPRESENTASJON.mdtests/fixtures/marp-export/media/diagram.svgportrait.svgDetails
From the project READMEPresentation Validation
Run the bundled read-only dispatcher against the explicit Project Folder:
presentation-validation check all --project-dir <project> --profile generation
presentation-validation check all --project-dir <project> --profile proofread
To check only the Media Spec role rule (media.diagram-roles) before Media
Specs are approved, run check media-spec with the generation profile.
The dispatcher never installs tools, acquires credentials, changes project files, or updates PROJECT.json. The phase-owning Skill remains responsible for state changes after validation succeeds.
Output voice
Apply a lightweight human-voice pass to human-readable validation reports. Name
the failing check, affected artifact, and remediation without puffery. Preserve
JSON output, exact paths, commands, error identifiers, and machine-readable
report contracts. Presentation-copy generation must already have completed the
required standalone unslop pass; validation does not substitute for it.
Use --format json when another agent or process needs structured findings. Use --report <path> only when a persistent report is explicitly requested.
Full validation is supported as part of the complete Presentation Skill Suite. A consumer Skill may explain that this Skill is unavailable, but focused installation is not a supported full-validation mode.
Maintenance
If resolving a real validation failure takes more than one ad hoc diagnostic/fix command, that's a signal, not a one-off: either the check is a false positive (failing for a reason unrelated to real presentation content) or the fix belongs in this Skill, not improvised against the Project Folder's output files each time it recurs. Promote it — fix the detector, or build the fixer in.
Worked example: Wayfinder: Fix presentation-validation's false-positive export detectors. exports.parity's PDF page counter and exports.media-parity's HTML reference scan were both false-positiving on Marp/Bespoke export artifacts (a compressed PDF object stream, a JS string literal inside <script>) after a proofread run needed several manual grep/node/ghostscript commands to work around them. Both detectors were fixed directly instead.