reversa-docs-publisher

Generates an offline-capable HTML documentation index with seals, navigation, and link validation.

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill reversa-docs-publisher-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-docs-publisher
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.agents/skills/reversa-docs-publisher
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill reversa-docs-publisher-tjsasakifln

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It consolidates scattered HTML documentation pages produced by multiple agents into a single coherent mini-site with a navigable index, consistent visual identity, and verified links that work offline and via file://. ## Core Features & Use Cases - Index and seal generation: Creates index.html with a hero seal SVG, injects a mini-seal and navigation menu retroactively into all existing pages. - Offline-first vendor bundling: Downloads pinned versions of Three.js, D3, and Highcharts into assets/vendor/ with CDN fallbacks so no page depends on external CDNs. - Auto-discovery and validation: Scans auxiliary HTMLs via meta tags, validates relative links, and runs an HTTP smoke test before reporting final telemetry. - Use Case: After three documentation agents generate architecture, metrics, and glossary pages, run this publisher to produce a unified index.html that opens with a double click, works without internet, and reports broken links or missing libraries. ## Quick Start Run the reversa-docs-publisher skill to regenerate the documentation index and inject the project seal into all pages in _reversa_docs/.

Frequently Asked Questions about reversa-docs-publisher

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

FAQPage Schema
How do I generate a documentation index page from multiple HTML files?▼

Run the publisher after the other documentation agents have produced their pages. It reads pagesGenerated from the state file, builds a nav array, and writes index.html with cards linking to every existing page plus discovered auxiliary HTMLs.

How to make a static HTML documentation site work offline without a CDN?▼

Download all third-party libraries into a local assets/vendor/ directory before rendering pages. The publisher uses a vendor-pins.yaml matrix with pinned versions and ordered CDN fallbacks, then rewrites script tags to point at local files.

Why do fetch calls fail when opening HTML files via file://?▼

Browsers block fetch() requests from pages with a null origin due to CORS rules. The solution is embedding JSON data directly into a JavaScript file like data.js and consuming it via a global object such as window.RV_DATA instead of fetching local files.

Does the publisher modify HTML files outside its output directory?▼

No. It only writes inside _reversa_docs/ and creates timestamped backups before overwriting files. Auxiliary HTMLs discovered in other directories are read-only and never modified or deleted.

What happens if a required JavaScript library cannot be downloaded?▼

The publisher records the missing library in the state file under vendorMissing and continues. Pages depending on that library receive a placeholder warning, and the final summary flags the issue in red.