Report Workshop

Problem

When a request combines material analysis, formal report writing, and HTML presentation, triggering separate skills can lose context, produce inconsistent artifacts, or let errors reach the final page without review. Report Workshop targets this composite workflow by chaining the three steps in a fixed order and pausing after each deliverable for user approval. It is especially suited to scenarios that need a path from raw source material to a presentable deliverable.

How It Works

The workflow runs three stages: Mt-analysis structures the source material into an analysis report; Official Document Writer turns that report into an official document or professional report, with Word and PDF outputs; and html-ppt renders a 5-15 page HTML visual report. Before each stage, it reads the corresponding sub-skill SKILL.md and references live instead of caching stale content. Outputs are archived under a dated folder such as YYYY-MM-DD-content, and updates are backed up as -backup vN before overwrite, making revision history easier to inspect.

Scope and Notes

It is best for tasks that explicitly need both material analysis and PPT/HTML-style reporting. If the user only needs analysis, writing, or page generation, the matching sub-skill should be used directly. The mandatory pause after every step suits human-in-the-loop review, but it is not ideal for fully unattended batch generation. It also expects clear materials and objectives, otherwise the review cost across steps will increase noticeably.