better-read-html

Generate or audit source-first static HTML artifacts with fidelity modes.

Updated May 26, 2026
One-click install
npx skills add https://github.com/XWIlluDelu/agent-share --skill better-read-html
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: better-read-html
Source: https://github.com/XWIlluDelu/agent-share/tree/main/lib/better-read-html
Command: npx skills add https://github.com/XWIlluDelu/agent-share --skill better-read-html

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It helps you create or validate source-first, browser-readable HTML that stays faithful to the original document text, with evidence-linked structure and a consistent, offline-friendly reader layout.

Core Features & Use Cases

  • Create static HTML artifacts (source-first) for papers, technical reports, notes, plans, and specifications when the user specifically wants an offline/local/single-file/printable HTML deliverable.
  • Choose a fidelity mode—preserve for exact conversion boundaries, annotate-synthesize for close reading and report-style explanation, or audit for verifying an existing HTML artifact.
  • Protect source integrity by keeping canonical content unchanged and marking generated/layout duplicates as noncanonical, with link and asset validation.
  • Use design that prioritizes readability with IBM Carbon-style, locally embedded CSS and structured semantic HTML (rails, figures, captions, equations, citations).
  • Detect common HTML integrity issues via the included auditor script (ids, internal links, missing assets, remote dependencies, canonical-text mismatch in supported cases).

Quick Start

Use better-read-html to render or audit your HTML artifact by running the provided HTML audit script against the file you generated.

Frequently Asked Questions about better-read-html

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

FAQPage Schema
How do I convert technical papers and reports into static HTML for offline reading?

To convert technical papers into static HTML, this tool generates source-first, browser-readable artifacts with embedded CSS and semantic structure. It preserves the original document text while applying an offline-friendly reader layout tailored for scholarly markup like figures, tables, and equations.

What is the best way to audit an existing HTML document for missing assets and broken internal links?

The best way to audit an existing HTML document is to run the included auditor script, which detects common integrity issues like missing assets, broken internal links, remote dependencies, and duplicate IDs to ensure your file is fully self-contained.

How do I preserve source integrity when converting documents to browser-readable HTML?

To preserve source integrity during HTML conversion, use the preserve fidelity mode. This keeps canonical content unchanged and explicitly marks any generated or layout duplicates as noncanonical, ensuring evidence-linked structure and original text boundaries are maintained.

Can I validate fidelity claims and canonical text boundaries in a converted HTML file?

Yes, you can validate fidelity claims by selecting the audit mode. This mode verifies an existing HTML artifact by checking canonical versus noncanonical text boundaries, validating links and assets, and detecting structural mismatches in supported cases.

When do I need to use a specific fidelity mode for HTML document conversion?

You need a specific fidelity mode based on your goal: use preserve for exact conversion boundaries, annotate-synthesize for close reading and report-style explanation, or audit for verifying an existing HTML artifact's integrity and evidence-linked structure.

Does the generated static HTML reader require remote dependencies or an internet connection?

No, the generated static HTML reader does not require remote dependencies. It uses locally embedded IBM Carbon-style CSS and structured semantic HTML to ensure the final artifact is fully offline-friendly and self-contained.