book-verify

Verify bookSHelf HTML output for structure, security, navigation, and accessibility.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/shuff57/agent-evo --skill book-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: book-verify
Source: https://github.com/shuff57/agent-evo/tree/main/skills/.archive/book-verify
Command: npx skills add https://github.com/shuff57/agent-evo --skill book-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill verifies the quality of HTML output from the bookSHelf pipeline, ensuring structural integrity, security, and accessibility.

Core Features & Use Cases

  • Comprehensive Quality Checks: Validates document structure, security, navigation, content classes, solution expandables, and accessibility.
  • Automated Verification: Integrated into the pipeline for seamless integration and efficiency.
  • Quick Start: Use the Skill to verify HTML output after book-html-gen and before book-publish.

Quick Start

Run the book-verify skill on the HTML file 'book-output.html'.

Frequently Asked Questions about book-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify HTML output quality for accessibility and security before publication?

To verify HTML output quality, run comprehensive automated checks on document structure, security, navigation, content classes, and accessibility to ensure publication-ready results.

What does an HTML quality check for polyfill.io presence and missing solution classes involve?

An HTML quality check scans output files to detect critical security issues like polyfill.io presence and structural flaws such as missing solution classes, preventing compromised publication.

How do I validate HTML structure and expandable solution elements in a pipeline?

To validate HTML structure and expandable solution elements in a pipeline, run verification scripts that check document integrity, content classes, and solution expandables before publishing.

Can I use automated verification scripts to check HTML accessibility in a publishing workflow?

Yes, automated verification scripts can be integrated directly into a publishing workflow to check HTML accessibility, ensuring structural integrity and compliance before final publication.

Why is HTML verification needed after generation and before publishing in a pipeline?

HTML verification is needed between generation and publishing to catch critical structural, security, and accessibility issues, ensuring only high-quality output reaches publication.

What are the limitations of automated HTML verification for content classes and navigation?

Automated HTML verification limitations include dependency on predefined checks for content classes and navigation, meaning it validates structural presence rather than subjective content quality.