How do I install the Cgpt Render Check skill?

Run npx skillmds@latest add pvsundar/cgpt-render-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cgpt Render Check safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cgpt Render Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cgpt Render Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cgpt Render Check?

pvsundar (@pvsundar) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cgpt Render Check by pvsundar — Agent Skill

Name: Cgpt Render Check
Author: pvsundar

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.

pvsundar Updated Sep 21, 2026

File contents

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

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.
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.
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.
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.
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:

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:

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.

---name: cgpt-render-checkdescription: 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.---# CGPT Render CheckUse 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 Checks1. 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 ScriptRun a first-pass structural check:```powershellpython C:\Users\sundar\.codex\skills\cgpt-render-check\scripts\render_check.py "C:\path\to\output.docx"```The helper accepts one or more files:```powershellpython 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.

Frequently asked questions