data-visualization

Assemble persisted research evidence into charts, statistics, and a markdown report.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/diankong720-ui/Pandora --skill data-visualization-diankong720-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-visualization
Source: https://github.com/diankong720-ui/Pandora/tree/main/skills/data-visualization
Command: npx skills add https://github.com/diankong720-ui/Pandora --skill data-visualization-diankong720-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-finalization visualization and report assembly stage. Consumes persisted session evidence and produces descriptive stats, chart assets, and a human-readable markdown report.

Core Features & Use Cases

  • Validate chart specs authored by the LLM
  • Consume only persisted session evidence to render charts, generate descriptive statistics, and assemble a final markdown report
  • Persist chart lineage and artifacts such as report_evidence.json, chart_spec_bundle.json, descriptive_stats.json, visualization_manifest.json, charts/.plot-data.json, charts/.png, and report.md

Quick Start

Run the data-visualization stage to assemble the final report artifacts from the persisted session evidence.

Frequently Asked Questions about data-visualization

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

FAQPage Schema
How do I generate charts and markdown reports from persisted session evidence?

Chart rendering and markdown report assembly consume persisted session evidence like final_answer.json and report_evidence.json to generate descriptive statistics, PNG charts, and a final report.md file.

What is the process for validating chart specifications before rendering visuals?

Chart spec validation checks LLM-authored chart specifications against persisted session data before rendering, ensuring only valid specs proceed to generate chart_spec_bundle.json and corresponding PNG artifacts.

Can I produce descriptive statistics and visualization artifacts using only persisted research data?

Yes, descriptive statistics generation and visualization artifact creation use only persisted session data to produce descriptive_stats.json, visualization_manifest.json, and charts/*.plot-data.json files.

Do I need final_answer.json persisted before running data visualization and report assembly?

Yes, final_answer.json and report_evidence.json must be persisted as prerequisite inputs, because the visualization stage consumes only persisted session evidence to produce the final artifact bundle.

What's the best way to assemble a visual report bundle from finalized research evidence?

Running the post-finalization visualization stage assembles the visual report bundle by validating chart specs, rendering PNG charts, generating descriptive stats, and persisting all artifacts including report.md.

Why does chart rendering require persisted session data instead of live inputs?

Chart rendering requires persisted session data to ensure chart lineage and artifact persistence maintain data integrity, producing reproducible visualization_manifest.json and chart assets from finalized evidence.