report-summarizing

Transform lengthy investigation reports into a four-layer Markdown report with Mermaid diagrams.

7|4|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/windschord/claude_skils --skill report-summarizing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-summarizing
Source: https://github.com/windschord/claude_skils/tree/main/report-summarizing
Command: npx skills add https://github.com/windschord/claude_skils --skill report-summarizing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill reorganizes lengthy research results or analyses into a four-layer report format (Executive Summary, Overview, Detailed Analysis, Appendix) to enable progressive disclosure for decision-makers, with clear navigation and visuals.

Core Features & Use Cases

  • Four-layer structure for progressive disclosure
  • Rich executive summaries with conclusions, recommendations, and key points
  • Overview section with PROS/CONS and課題/対策 tables
  • Detailed analysis for implementation guidance
  • Mermaid diagrams for visualizing structure
  • Appendix for code changes and technical specifications
  • Internal navigation across sections

Quick Start

  • Request: "Convert this investigation into an executive summary format" or "Summarize this report into four layers"
  • Provide findings and data, and let the system structure the report with links to detailed sections

Frequently Asked Questions about report-summarizing

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

FAQPage Schema
How do I convert a lengthy research report into an executive summary?

Transform your report into a four-layer structure: Executive Summary with conclusions and recommendations, Overview with PROS/CONS analysis, Detailed Analysis for implementation guidance, and Appendix for technical specifications. This progressive disclosure format lets decision-makers find answers at their reading depth.

What's the best way to structure findings for decision-makers?

Organize findings into four layers with explicit navigation between sections. Lead with the Executive Summary containing key conclusions and recommendations, follow with Overview-level PROS/CONS and risk/mitigation tables, reserve implementation details and code changes for Detailed Analysis and Appendix. This separation ensures decision-ready outputs.

Can I use Mermaid diagrams and Markdown in my executive reports?

Yes. The four-layer report format supports Mermaid diagrams for visualizing structure and renders fully in Markdown for GitHub and VSCode compatibility. Technical visuals integrate throughout the Overview and Detailed Analysis layers.

How do I separate technical details from high-level summaries?

Place conclusions, recommendations, and PROS/CONS in the Executive Summary and Overview layers for decision-makers. Move code changes, specifications, and detailed implementation guidance into the Detailed Analysis and Appendix layers, with cross-layer navigation links.

When should I use a four-layer report structure instead of a flat summary?

Use four-layer structure when stakeholders have different information needs: executives need conclusions and recommendations, technical leads need PROS/CONS and risk analysis, and engineers need implementation details. Progressive disclosure prevents information overload.