Index of every page on this site: llms.txt
All skills
markdown-viewer avatar

/documd-visuals

@2672b69
by Markdown Viewermarkdown-viewer/skills3.4k stars
192
Run it yourself

Create text-driven visuals in Markdown: charts, diagrams, cards, architecture and page layouts. Charts and analytical views (bar, line, pie, heatmap, correlation, regression); reliability and operations (latency, incident, throughput, cycle time, OKR, standup, on-call); product and finance (funnel, retention, revenue, budget); process and workflow (approval, BPMN); software design and behaviour (class, state machine, sequence, C4); dependencies and impact (dependency graph, ER, causality); system architecture as HTML (layer stack, wings, zones, topology, service catalogue, request paths); infrastructure (cloud, Kubernetes, ETL, network, security, IAM, compliance); governance and people (ArchiMate, org chart, hiring); knowledge and planning (mind map, roadmap, Gantt, migration); documents (comparison, SWOT, memo, policy, catalogue, case study). Use when a document needs a diagram, chart or card. Figures render live. Not for slide decks or math notation. Not recommended: mermaid / canvas / drawio / dot.

Use this Skill: https://skilld.dev/gh/markdown-viewer/skills/documd-visuals

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplesops-monitoringheatmap-incident-load.md

Heatmap — Incident Load by Day and Hour (ECharts)

Best for: showing intensity across two ordered dimensions such as day/hour, team/week, or product/region Avoid when: the reader needs exact values for every cell or the matrix is extremely sparse (use a table or dots) Answers: when concentration peaks happen, and which rows or columns stay consistently heavy or light

{
  "color": ["#2b66c4", "#2f9e44", "#f3a33c", "#d1242f", "#7048e8", "#0f9b9b", "#c16f8a", "#7c5a3d"],
  "width": 860,
  "height": 420,
  "title": {
    "text": "Incident Load by Day and Hour",
    "subtext": "Last four weeks aggregated",
    "left": "left",
    "top": 10,
    "itemGap": 14,
    "subtextStyle": { "lineHeight": 18 }
  },
  "grid": { "left": 88, "right": 36, "top": 118, "bottom": 48 },
  "xAxis": {
    "type": "category",
    "data": ["00", "04", "08", "12", "16", "20"],
    "splitArea": { "show": true }
  },
  "yAxis": {
    "type": "category",
    "data": ["Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun"],
    "splitArea": { "show": true }
  },
  "visualMap": {
    "show": false,
    "min": 0,
    "max": 24,
    "inRange": {
      "color": ["#2b66c4", "#2f9e44", "#f3a33c"]
    }
  },
  "series": [
    {
      "name": "Incidents",
      "type": "heatmap",
      "label": { "show": true, "fontSize": 10 },
      "emphasis": { "itemStyle": { "shadowBlur": 6, "shadowColor": "rgba(0, 0, 0, 0.25)" } },
      "data": [
        [0, 0, 6], [1, 0, 4], [2, 0, 9], [3, 0, 14], [4, 0, 18], [5, 0, 10],
        [0, 1, 5], [1, 1, 3], [2, 1, 8], [3, 1, 12], [4, 1, 16], [5, 1, 9],
        [0, 2, 4], [1, 2, 4], [2, 2, 7], [3, 2, 11], [4, 2, 15], [5, 2, 8],
        [0, 3, 7], [1, 3, 6], [2, 3, 10], [3, 3, 16], [4, 3, 24], [5, 3, 13],
        [0, 4, 8], [1, 4, 7], [2, 4, 12], [3, 4, 18], [4, 4, 22], [5, 4, 14],
        [0, 5, 3], [1, 5, 2], [2, 5, 4], [3, 5, 6], [4, 5, 8], [5, 5, 5],
        [0, 6, 2], [1, 6, 2], [2, 6, 3], [3, 6, 5], [4, 6, 7], [5, 6, 4]
      ]
    }
  ]
}

Key Options

Option Effect
series.type: "heatmap" Encodes value by color on a 2D categorical grid
visualMap Maps values to color; in tight static exports it can stay hidden while still driving the palette
splitArea.show Makes each grid cell legible in export, especially on dark themes
label.show Useful for compact report-size matrices where every cell count still matters
grid Heatmaps need extra left/bottom room because both axes carry full labels

Data Shape

Each item is [xIndex, yIndex, value], where xIndex maps into xAxis.data and yIndex maps into yAxis.data. Keep both axes ordered, because heatmaps depend on adjacency.

Pitfalls

  • ❌ Unordered categories on either axis → ✅ heatmaps only work when neighboring cells have a meaningful sequence
  • ❌ Color-only heatmap with no numbers or scale → ✅ in static exports, keep labels on, or show a visible visualMap when layout allows
  • ❌ Huge sparse matrices with many zeros → ✅ use dots or a table when empty cells dominate
  • ❌ Depending on hover for exact values → ✅ static exports need either labels or a small enough grid to read directly

Alternatives

Variant Use instead
Time trend by one measure trend-line-multi-series.md
Exact row/column comparison comparison-bars.md
Day-level density over long periods calendar-release-pace.md
<!-- source: ECharts option manual (series-heatmap / visualMap / splitArea) + examples gallery heatmap family -->

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts16d3 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides documentation and examples for creating various visuals in Markdown using engines like ECharts, Vega, PlantUML, and HTML. It recommends using the vendor-owned @markdown-viewer/documd CLI tool for document conversion and verification. The skill itself contains no executable code or malicious patterns.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

Signed by skilld at 2672b69. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 weeks ago.

Activeupdated 3 weeks ago
Other metadata
compatibility
Figures are text in the Markdown — fenced blocks or bare HTML — and the host viewer renders them live: nothing to pre-render, build or install. Export to html / epub / docx / pdf is optional and needs Node 18+ and Chrome/Chromium, via `npx @markdown-viewer/documd`.

README badge

README badge for markdown-viewer/skills