# Validate Epub Project

> Validate EPUB ebook projects before release or bookstore upload. Use when asked to check whether an EPUB is ready, run EPUBCheck, rebuild a release package, inspect generated EPUB contents, verify images and CSS, scan Google Play Books warning patterns, audit dist folders, or report final publishing readiness.

- Skill: `j945935cy/validate-epub-project` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add j945935cy/validate-epub-project`
- Raw SKILL.md: https://api.skillmd.com/api/skills/j945935cy/validate-epub-project/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: j945935cy (https://skillmd.com/u/j945935cy)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/j945935cy/validate-epub-project

---


# Validate EPUB Project

## Core Workflow

Use this skill to validate an EPUB project end to end. Prefer existing project scripts over ad hoc commands.

1. Inspect project shape:
   - Locate `manuscript/`, `metadata/`, `styles/`, `assets/`, `tools/`, `output/`, and `dist/`.
   - Locate scripts such as `tools/package-release.ps1`, `tools/validate-project.ps1`, `tools/build-epub.ps1`, and `tools/check-epub.ps1`.
2. Rebuild the current release when requested or when validation must reflect latest source:
   - Use the project packaging script if available.
   - If a version is needed, infer it from README, PROJECT_STATUS, package script defaults, or the latest `dist/v*` folder.
3. Run validation:
   - EPUBCheck or the repo wrapper.
   - Release audit if present.
   - Internal EPUB inspection for metadata, resource counts, CSS, and image inclusion.
4. Scan bookstore-warning patterns:
   - Google Play Books often reports unsupported CSS from Pandoc syntax highlighting or vendor-specific properties.
   - Search generated EPUB internals, not only source CSS.
5. Check release artifacts:
   - EPUB, cover, preview, listing docs, checklist, manifest, and checksums.
   - Confirm the exact file path the user should upload.
6. Report readiness:
   - Findings first if anything blocks publishing.
   - Otherwise say clearly that validation passed and list upload paths.

## Useful Commands

For this user's Windows/PowerShell ebook projects, use:

```powershell
powershell -ExecutionPolicy Bypass -File .\tools\package-release.ps1 -Version <version>
```

```powershell
powershell -ExecutionPolicy Bypass -File .\tools\check-epub.ps1
```

```powershell
Get-ChildItem -LiteralPath .\dist\v<version> | Select-Object Name,Length
```

For deeper checks, read `references/checks.md`.

## What To Report

Include:

- EPUBCheck result.
- Google Play Books CSS warning scan result.
- Number of XHTML/CSS/image resources if inspected.
- Upload EPUB path.
- Upload cover path.
- Whether release folder audit passed.
- Any untracked files that may matter.

Do not push, submit, delete release files, or upload to a bookstore without explicit user confirmation.