reversa-docs-publisher

Bundle vendor assets and compile HTML metadata into an offline documentation site.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-docs-publisher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-docs-publisher
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-docs-publisher
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-docs-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the problem of turning scattered reverse engineering outputs and auxiliary HTML fragments into a coherent, navigable documentation mini site that works offline and consistently.

Core Features & Use Cases

  • Offline-first mini site bundling: it downloads required third-party libraries into local assets/vendor/ so the generated pages work via file:// without external CDN dependencies.
  • Deterministic identity via generative seals: it generates a large hero seal and a matching mini seal (based on the project seed) and injects them across all pages.
  • Single-source data + safe navigation: it compiles all intermediate JSON artifacts into one assets/js/data.js, injects window.RV_DATA, builds nav links from discovered pages, validates relative links, and updates .state.json telemetry including smoke test results.

Quick Start

Run the reversa-docs-publisher skill with the command reversa-docs-publisher to produce .reversa/documentation/index.html and inject the mini seal and navigation across the generated documentation pages.

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 an offline documentation site from scattered HTML fragments?

To generate an offline documentation site, you bundle local vendor assets, inject project seals, compile HTML metadata into a single window.RV_DATA payload, and produce navigable pages that run under file:// without external fetch calls.

Why does my static documentation site fail to load assets when opened via the file protocol?

Static documentation sites fail under file:// when they rely on external CDN fetches. This Skill solves it by downloading third-party libraries into local assets/vendor/ directories, ensuring all pages work offline with vendor-local dependencies only.

What is the best way to bundle reverse engineering HTML outputs into a navigable mini site?

The best way to bundle reverse engineering HTML outputs is compiling intermediate JSON artifacts into a single data.js file, building navigation links from discovered pages, and validating relative links to create a coherent offline mini site.

Can I use generated static site pages without any internet connection or CDN dependencies?

Yes, you can use generated static site pages without an internet connection. The Skill enforces an offline-first constraint by downloading all required third-party libraries locally and injecting a single window.RV_DATA payload, eliminating external CDN dependencies.

How do I track smoke test and telemetry outcomes across generated documentation pages?

You track smoke test and telemetry outcomes by recording the results into a .state.json file. The Skill updates this state file during the finalization pipeline after validating relative links and injecting navigation across all pages.

Does the documentation mini site generator support unique visual identity for each project?

Yes, the documentation mini site generator supports unique visual identity. It generates a large hero seal and a matching mini seal based on a project seed, injecting these deterministic seals across all generated pages for consistent branding.