Visual storytelling

Skill fabioc-aloha/Alex_Skill_Mall/plugins/data-analytics/visual-storytelling

Bundle plugin: installs the complete Visual Storytelling pipeline (brief, ingest, clean, select, deliver). See component SKILLs for detailed specs.From its SKILL.md

Install

npx -y skills add fabioc-aloha/Alex_Skill_Mall --skill visual-storytelling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 609 tokens by cl100k_base, as published. Nobody here has run it

Visual Storytelling (Bundle)

This is the entry point for the Visual Storytelling pipeline. It installs 7 component plugins and an orchestrator agent.

Pipeline

Brief -> Ingest -> Clean -> Select -> Deliver

Brief (storytelling-requirements): Structured intake producing audience, Big Idea, questions with communication goals, data sources, delivery target.
Ingest (datasource-connectors): Load from CSV, JSON, API, SQL, Excel, Parquet with error handling and encoding detection.
Clean (data-preparation): Profile, clean, aggregate, pivot, quality-check.
Select (visual-vocabulary): Map each question's communication goal to the right chart type using the visual vocabulary catalog.
Deliver: Render to the chosen format:
- delivery-ascii-dashboard -- terminal/plain text (78-char aligned)
- delivery-svg-markdown -- GitHub-compatible static SVG (D3.js patterns)
- delivery-html-dashboard -- interactive HTML (Apache ECharts v6)

Orchestrator Agent

The visual-storytelling agent runs the full pipeline. Invoke it with a data source, a rough request, and a delivery target. It produces a structured brief, delegates to each pipeline step, and runs a CSAR QA loop on the output.

Component Skills

Each component has its own detailed SKILL.md. This bundle skill is a routing layer; the real specs live in the components:

Component	SKILL Path
`storytelling-requirements`	`.github/skills/local/storytelling-requirements/SKILL.md`
`datasource-connectors`	`.github/skills/local/datasource-connectors/SKILL.md`
`data-preparation`	`.github/skills/local/data-preparation/SKILL.md`
`visual-vocabulary`	`.github/skills/local/visual-vocabulary/SKILL.md`
`delivery-ascii-dashboard`	`.github/skills/local/delivery-ascii-dashboard/SKILL.md`
`delivery-svg-markdown`	`.github/skills/local/delivery-svg-markdown/SKILL.md`
`delivery-html-dashboard`	`.github/skills/local/delivery-html-dashboard/SKILL.md`

When to Use Which Delivery

Need	Format	Why
GitHub README	SVG	No JS execution on GitHub
Terminal output	ASCII	Universal, no rendering needed
Interactive exploration	HTML	Tooltips, zoom, legend toggle
Static docs / reports	SVG	Crisp at any scale, inline in Markdown
Presentations	HTML	Open in browser, full-screen
Offline / no CDN	SVG or ASCII	No external dependencies