codex-html-report

Create self-contained HTML reports with embedded CSS and editorial layouts.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Canepro/codex-skills --skill codex-html-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-html-report
Source: https://github.com/Canepro/codex-skills/tree/main/skills/codex-html-report
Command: npx skills add https://github.com/Canepro/codex-skills --skill codex-html-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps produce browser-native, self-contained HTML reports for durable Codex artifacts, ensuring artifacts remain readable and accessible outside live chats.

Core Features & Use Cases

  • Use for post-case artifacts such as implementation closeouts, deployment verification, code reviews, architecture plans, research briefs, or complex explanations that benefit from a structured, editorial layout with sections, evidence, and timelines.
  • Produces a single-file HTML report with embedded styling and an editorial rhythm designed for dark-first readability and offline viewing.
  • Supports a durable narrative with an evidence rail, timelines, and clearly stated status to aid handoffs and audits.

Quick Start

Generate a self-contained HTML report for this work artifact.

Frequently Asked Questions about codex-html-report

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

FAQPage Schema
How do I generate a self-contained HTML report from an incident response or code review?

To generate a self-contained HTML report, the skill compiles incident responses, code reviews, and timelines into a single file with embedded CSS for offline viewing and human-readable proof.

What is the best way to create an offline HTML artifact for project closeouts and architecture decisions?

The best way to create an offline HTML artifact is using a browser-native format that embeds CSS and avoids external assets, ensuring project closeouts and architecture decisions remain durable and readable.

Can I use this to compile evidence and timelines into a single HTML file?

Yes, you can compile evidence and timelines into a single HTML file. It structures status updates and proof into a dark-first editorial layout designed for audits and handoffs.

Does the generated HTML report require external assets or dependencies to render correctly?

The generated HTML report requires no external assets or dependencies to render correctly. It uses embedded CSS within a single self-contained file to guarantee browser-native readability offline.

How do I structure a deployment verification document as a durable narrative?

To structure a deployment verification document as a durable narrative, the skill applies an editorial rhythm with an evidence rail and timelines, formatting complex explanations into a readable proof artifact.

When should I not use a single-file HTML format for documentation?

You should not use a single-file HTML format for documentation when you need dynamic data integration or server-side interactivity, as this approach strictly produces static, self-contained offline artifacts.