# Cgpt Render Check

> Validate rendered documents and presentation outputs after Quarto, Pandoc, python-pptx, document export, HTML generation, PDF export, or report build work. Use when the user asks to check, validate, QA, inspect, smoke test, or deliver a rendered DOCX, PPTX, PDF, HTML, Markdown, or generated report.

- Skill: `pvsundar/cgpt-render-check` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add pvsundar/cgpt-render-check`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pvsundar/cgpt-render-check/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: pvsundar (https://skillmd.com/u/pvsundar)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/pvsundar/cgpt-render-check

---


# CGPT Render Check

Use this skill after generating or editing a deliverable. Do not call an output clean until the relevant checks have run or you have explicitly reported why they could not run.

## Core Checks

1. File presence and size.
   - Confirm the output exists.
   - Warn if it is empty or suspiciously small.
   - When there are multiple related outputs, check every file named by the user rather than only the primary file.

2. Container integrity.
   - DOCX and PPTX must be valid ZIP packages.
   - DOCX should contain `[Content_Types].xml` and `word/document.xml`.
   - PPTX should have real slide XML files and no broken slide references.
   - PDF should have a valid `%PDF-` header and a normal EOF marker; use a PDF library or `pdfinfo` when available.
   - HTML should contain normal document structure.
   - HTML should be checked for obvious missing local image/script assets and missing internal anchors.

3. Render artifacts.
   - Search extracted text or raw HTML/Markdown for unresolved markers: `??`, `undefined`, missing figure text, raw LaTeX commands, or obvious template placeholders.
   - For HTML reports, check that expected tables/cards/sections are present when the request named them.
   - Treat unresolved text findings as possible source-content defects, not only container defects.

4. Source gotchas when applicable.
   - Quarto/Pandoc: inspect nearby `.qmd`, `.yml`, `.bib`, and asset paths when a render fails.
   - Decks: verify slide count, title text, and any project-specific font floor or brand constraints.
   - Web outputs: open the page with the Browser skill when visual layout or interaction matters.
   - DOCX/PPTX: if the structural check passes but formatting matters, render pages or slide thumbnails before claiming visual quality.

5. Report a concise result.
   - Use PASS/WARN/FAIL.
   - Include exact file path, file type, file size, checks run, and fixes needed.
   - Distinguish hard failures from warnings that need human review.

## Helper Script

Run a first-pass structural check:

```powershell
python C:\Users\sundar\.codex\skills\cgpt-render-check\scripts\render_check.py "C:\path\to\output.docx"
```

The helper accepts one or more files:

```powershell
python C:\Users\sundar\.codex\skills\cgpt-render-check\scripts\render_check.py "C:\path\to\report.html" "C:\path\to\deck.pptx"
```

The script is intentionally conservative. It catches structural corruption, common unresolved render markers, weak HTML structure, missing local HTML assets, and basic DOCX/PPTX/PDF package problems. Visual QA still requires opening, rendering, or screenshotting the file when layout matters.