This skill should be used when the user asks to "KDP audit", "check manuscript formatting", "is my book ready for KDP", "Amazon publishing requirements", "Kindle formatting check", "manuscript readiness", "book formatting audit", "prepare for Amazon KDP", or mentions KDP/Amazon publishing compliance. It audits a book manuscript against Amazon KDP (Kindle Direct Publishing) requirements for both eBook and paperback formats, handling technical books (LaTeX, math-heavy) and fiction/general nonfiction.
From kdpnpx claudepluginhub queelius/claude-anvil --plugin kdpThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Audit a book manuscript against Amazon KDP (Kindle Direct Publishing) requirements and produce a structured gap report. This skill evaluates interior formatting, cover specs, metadata completeness, and genre-specific requirements (technical vs. fiction).
Identify manuscript files and format. Look for these file types in the current directory or specified path:
Primary manuscript formats (Glob tool):
.tex files (LaTeX manuscripts, common for technical books).docx files (Microsoft Word, common for fiction/nonfiction).epub files (eBook source).md files (Markdown manuscripts).pdf files (final output).kpf files (Kindle Create project)Manuscript type classification:
If no manuscript is found, ask the user which file to audit.
Read .claude/kdp.local.md if it exists (Read tool). Extract the kdp configuration section and author metadata from YAML frontmatter. The config may include:
kdp:
trim_size: "6x9"
paper_type: "white"
binding: "paperback"
genre: "technical"
target_page_count: 300
author:
name: "Author Name"
bio: "Brief author bio"
If the file is missing, inform the user and offer to create one from the template at ${CLAUDE_PLUGIN_ROOT}/docs/user-config-template.md.
Trim size validation:
Margin requirements (varies by page count):
Font requirements:
Page numbers and headers/footers:
Table of Contents (Read/Grep tools):
Kindle eBook cover (file check via Glob tool):
cover*.jpg, cover*.jpeg, cover*.tiff, ebook-cover.*Paperback cover (if applicable):
paperback-cover.pdf, full-cover.pdf, cover-print.*Actual dimension verification (Bash tool):
identify (ImageMagick) is available: identify -format "%wx%h" cover.jpgfile cover.jpg which often reports dimensionsCover content requirements:
If cover files don't exist, note as a critical gap.
Required metadata:
Pricing and rights:
Grep for metadata in manuscript front matter or config. If missing, list what needs to be provided via KDP dashboard.
If manuscript is technical (LaTeX, math-heavy, code listings):
LaTeX compilation (Bash tool):
cd /path/to/manuscript && pdflatex -interaction=nonstopmode manuscript.tex
Verify compilation succeeds with no critical errors.
Math rendering:
\usepackage{amsmath} or equivalentCode listings:
listings or minted package usageIndex and bibliography:
\printindex and \bibliography{} commands present\index{}).bib file exists and is referencedmakeindex and bibtex successfullyCheck for eBook-specific issues that affect Kindle rendering and KDP acceptance.
EPUB validation (Glob tool, Bash tool):
.epub files exist in the projectepubcheck is available (which epubcheck), run it on the EPUB file and report resultsepubcheck is not installed, note it as a recommendation and list common EPUB issues to manually check:
.md or .docx source files do, recommend conversion via Pandoc before audit:
pandoc manuscript.md -o manuscript.epub --toc --metadata title="Book Title"
Check for issues that specifically break on Kindle devices:
Footnotes (Grep tool):
\footnote in LaTeX source, or footnote markers in DOCX/HTMLWide tables (Grep tool):
Complex CSS (Grep tool):
Large images (Bash tool):
ls -la on image files or identify if ImageMagick is availableIf manuscript is fiction or narrative nonfiction:
Chapter structure (Grep tool):
Front matter order validation (Grep/Read tools):
Back matter order validation (Grep/Read tools):
Scene breaks and formatting:
* * * or similar (not just blank lines)Scene break consistency (Grep tool):
* * *, all ---, all ###, etc.)Special elements:
Format the report as:
# KDP Audit Report: {book title}
## Summary
- **Status**: READY / NEEDS WORK / NOT READY
- **Manuscript type**: Technical / Fiction / Nonfiction
- **Format**: LaTeX / DOCX / EPUB / PDF
- **Target**: eBook only / Paperback only / Both
## Critical Gaps (Must Fix)
1. [Issue description] — [file:line] — [how to fix]
## Warnings (Should Fix)
1. [Issue description] — [recommendation]
## Interior Formatting
- [ ] or [x] Trim size: {size} (supported: yes/no)
- [ ] or [x] Margins: inside {calc}, outside {val}, top {val}, bottom {val}
- [ ] or [x] Fonts embedded and standard
- [ ] or [x] Page numbers start after front matter
- [ ] or [x] Table of Contents present and functional
## Cover Specifications
- [ ] or [x] eBook cover: {resolution}, {ratio}, {format}
- [ ] or [x] Paperback cover: {resolution}, spine width {calc}
- [ ] or [x] Cover dimensions verified: {actual} (required: {minimum})
## Metadata
- [ ] or [x] Title and subtitle
- [ ] or [x] Description/blurb (<4000 chars)
- [ ] or [x] Categories (up to 3 BISAC codes)
- [ ] or [x] Keywords (up to 7)
- [ ] or [x] Author bio present
## Technical Books Only
- [ ] or [x] LaTeX compiles successfully
- [ ] or [x] Math rendering correct
- [ ] or [x] Code listings formatted
- [ ] or [x] Index and bibliography present
## Fiction Only
- [ ] or [x] Front matter order: title -> copyright -> dedication -> TOC
- [ ] or [x] Back matter includes About the Author
- [ ] or [x] Scene breaks use consistent markers
- [ ] or [x] Scene breaks clearly marked
- [ ] or [x] Dialog formatting consistent
- [ ] or [x] Paragraph indentation correct
## eBook Validation
- [ ] or [x] EPUB validates (epubcheck)
- [ ] or [x] No Kindle-breaking issues (footnotes, wide tables, complex CSS)
## Recommended Next Steps
1. [Ordered list of actions to reach READY status]
After presenting the report, offer to fix issues that can be automated:
geometry packageFor complete KDP requirements and submission workflow, consult:
${CLAUDE_PLUGIN_ROOT}/docs/kdp-reference.md — Full KDP formatting requirements, cover templates, metadata guidelines, and submission checklist