dashboard-reporting

Aggregate verification results and progress logs into a self-contained HTML dashboard.

13|4|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/memect/kc --skill dashboard-reporting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dashboard-reporting
Source: https://github.com/memect/kc/tree/main/template/skills/zh/dashboard-reporting
Command: npx skills add https://github.com/memect/kc --skill dashboard-reporting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a self-contained HTML dashboard to visualize verification results, system progress, and quality metrics, enabling developers to quickly assess health and trends without setup overhead.

Core Features & Use Cases

  • Self-contained HTML dashboard: an offline-capable, shareable report that opens directly in a browser.
  • Per-rule and summary views: quick insights into accuracy, pass/fail counts, and detailed failure cases.
  • On-demand visualization: ideal after test rounds, production batches, or manager reviews to communicate status.

Quick Start

Run the dashboard generator on your results directory to produce a single HTML file.

Frequently Asked Questions about dashboard-reporting

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

FAQPage Schema
How do I generate a self-contained HTML dashboard from verification results?

To generate a self-contained HTML dashboard, the reporting tool aggregates your verification results and progress logs into a single offline-capable HTML file. It processes per-rule metrics and failure case details to visualize status and trends directly in a browser.

Can I visualize test round results and production logs without installing external dependencies?

You can visualize test round results and production logs without external dependencies because the dashboard generator runs entirely on the standard library. It creates a shareable HTML report that requires no setup overhead to view in a browser.

What is the best way to communicate verification status and trends to stakeholders?

The best way to communicate verification status to stakeholders is by using an on-demand HTML dashboard. It provides summary views alongside detailed failure cases, making it ideal for stakeholder reviews after production batches or test rounds.

Does the HTML reporting tool show per-rule metrics and failure case details?

Yes, the HTML reporting tool displays per-rule metrics and failure case details. It aggregates these verification results into both summary views and detailed reports, allowing developers to quickly assess accuracy and pass/fail counts.

Are there limitations when using a standard library HTML dashboard generator for reporting?

A limitation of using a standard library HTML dashboard generator is that it produces static, offline reports rather than live, interactive dashboards. It is designed for post-run visualization of verification results, not real-time monitoring.

When do I need a self-contained HTML report for my verification progress logs?

You need a self-contained HTML report when you want to share verification progress logs in an offline-capable format. It is ideal after test rounds or production runs to communicate status and quality metrics without requiring recipients to install additional software.