save-report

Classify conversation outputs and write numbered HTML reports to output-config.toml paths.

1|1|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/ntaksh42/env --skill save-report-ntaksh42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-report
Source: https://github.com/ntaksh42/env/tree/main/claude/skills/save-report
Command: npx skills add https://github.com/ntaksh42/env --skill save-report-ntaksh42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically save outputs from conversations (reviews, investigations, bug analyses) as structured HTML reports.

Core Features & Use Cases

  • Classifies the type of output (review, investigation, bug analysis, or research) and renders it into a numbered HTML document.
  • Writes the HTML file to the location specified by output-config.toml, enabling consistent archival storage.
  • Uses the provided templates to produce polished, self-contained HTML reports that include summaries, sections, and code blocks.

Quick Start

Tell the agent to save the latest results as a numbered HTML report to the configured location.

Frequently Asked Questions about save-report

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

FAQPage Schema
How do I automatically save code review results as an HTML report?

You can automatically save code review results as an HTML report by instructing the agent to classify the output and render it into a numbered HTML document using predefined templates, which is then written to a configured storage location.

How does saving bug analysis outputs as structured HTML documents work?

Saving bug analysis outputs as structured HTML documents works by classifying the conversation type, rendering the content with templates into a self-contained file with summaries and code blocks, and storing the numbered document at the path specified in configuration.

What is the best way to archive investigation findings from a conversation into a numbered file?

The best way to archive investigation findings into a numbered file is to use an automated rendering process that classifies the output type and writes the final HTML document to a consistent archival path defined by a configuration file.

Do I need a configuration file to specify the output path for generated HTML reports?

Yes, you need an output configuration file to specify the output path for generated HTML reports. The system reads the designated storage location from this file to consistently write and archive the numbered HTML documents.

Can I use custom templates to produce self-contained HTML reports with code blocks?

Yes, you can use provided templates to produce polished, self-contained HTML reports. The rendering process incorporates summaries, sections, and code blocks directly into the final document structure.

What types of conversation outputs can be classified and rendered into HTML reports?

Conversation outputs that can be classified and rendered into HTML reports include code reviews, investigations, bug analyses, and research findings, each structured into a numbered document with summaries and code blocks.