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-monitoringmatrix-service-scorecards.md

Matrix — Service Scorecards as a Metric Grid (ECharts)

Best for: comparing several entities against the same set of metrics in one aligned grid where position matters as much as value Avoid when: the reader needs one full chart per entity, or the values are better understood as trends over time Answers: which service/metric cells are strongest or weakest, and where the outliers cluster in the grid

{
  "color": ["#2b66c4", "#2f9e44", "#f3a33c", "#d1242f", "#7048e8", "#0f9b9b", "#c16f8a", "#7c5a3d"],
  "width": 900,
  "height": 420,
  "title": { "text": "Service Scorecards", "subtext": "Errors, latency, and satisfaction by team", "left": "left" },
  "matrix": {
    "left": 110,
    "top": 108,
    "right": 40,
    "bottom": 52,
    "x": {
      "data": ["Core", "Billing", "Search", "Identity", "Orders", "Warehouse"]
    },
    "y": {
      "data": ["Err", "Lat", "CSAT"]
    }
  },
  "visualMap": {
    "show": false,
    "min": 0,
    "max": 100,
    "inRange": {
      "color": ["#2b66c4", "#2f9e44", "#f3a33c"]
    }
  },
  "series": [
    {
      "type": "heatmap",
      "coordinateSystem": "matrix",
      "label": { "show": true, "fontSize": 11 },
      "data": [
        ["Core", "Err", 18], ["Billing", "Err", 26], ["Search", "Err", 14], ["Identity", "Err", 22], ["Orders", "Err", 31], ["Warehouse", "Err", 19],
        ["Core", "Lat", 54], ["Billing", "Lat", 62], ["Search", "Lat", 49], ["Identity", "Lat", 58], ["Orders", "Lat", 67], ["Warehouse", "Lat", 45],
        ["Core", "CSAT", 88], ["Billing", "CSAT", 81], ["Search", "CSAT", 91], ["Identity", "CSAT", 84], ["Orders", "CSAT", 76], ["Warehouse", "CSAT", 89]
      ]
    }
  ]
}

Key Options

Option Effect
matrix Declares the row/column grid and its labels directly
coordinateSystem: "matrix" Lets the series snap to named matrix cells rather than a cartesian grid
Hidden visualMap Drives the color scale while the cell labels carry the exact values
Heatmap cell labels Makes each score readable in a static export
Shared matrix axes Keeps every service/metric intersection aligned in one consistent plane

Data Shape

Each datum is [xCategory, yCategory, value], where both categories must exist in the matrix x.data and y.data definitions.

Pitfalls

  • ❌ Too many rows/columns in one frame → ✅ once labels shrink too far, the matrix loses its comparison advantage
  • ❌ No visible value labels or clear color mapping → ✅ in static exports, numbers or a visible legend have to carry the precision
  • ❌ Mismatched category names between matrix axes and data rows → ✅ one typo sends a cell nowhere
  • ❌ Expecting matrix to behave like repeated cartesian grids → ✅ it is its own coordinate system with named cells

Alternatives

Variant Use instead
One overlaid multi-series chart comparison-bars.md or trend-line-multi-series.md
One heatmap over two ordered axes heatmap-incident-load.md
Hierarchical portfolio views treemap-portfolio-breakdown.md
<!-- source: ECharts option manual (matrix coordinate system, layout on matrix) + v6 matrix examples -->

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