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.

examplesincident-managementincident-escalation-path.md

≈593 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Incident Escalation Path — Who Picks Up Next (Infographic)

Best for: one page that answers "the alert fired, who is responsible now?" Avoid when: the flow branches heavily (use a full flowchart in plantuml) Answers: the escalation ladder, the trigger for each hop, and where the path ends

infographic
theme
  colorPrimary #2b66c4
  palette
    - #2b66c4
    - #2f9e44
    - #f3a33c
    - #d1242f
    - #7048e8
    - #0f9b9b
    - #c16f8a
    - #7c5a3d
design
  structure relation-dagre-flow
  item simple-circle-node
data
  title Incident Escalation Ladder
  desc Each edge names the condition that causes the hand-off
  nodes
    - id alert
      label Alert fires
    - id oncall
      label On-call engineer
    - id lead
      label Team lead
    - id vendor
      label Vendor escalation
    - id postmortem
      label Postmortem
  relations
    - from alert
      to oncall
      label paged in 5 min
    - from oncall
      to lead
      label unresolved after 1 hour
    - from lead
      to vendor
      label platform defect confirmed
    - from oncall
      to postmortem
      label service restored

Data Shape

nodes (with id and human label) plus relations; each relation carries the condition as its label. The dagre layout handles a fan-out to two different next steps, which a plain sequence cannot.

Key Options

Option Effect
design structure relation-dagre-flow Directed layout with automatic rank ordering
design item simple-circle-node Circle nodes; rounded-rect-node suits longer labels
relation-network-* templates Use for undirected topology instead of a directed path

Pitfalls

  • ❌ infographic relation-dagre-flow as an entry line → ✅ no such template exists; declare the structure in a design block
  • ❌ Unlabelled edges → ✅ the trigger condition is the most useful part of each arrow
  • ❌ Drawing the whole incident process → ✅ escalation only; diagnostics belong in the runbook

Alternatives

Variant Use instead
Linear response steps incident-response-runbook.md
Service topology without direction service-dependency-network.md
Handover across shifts support-shift-handover.md
<!-- source: AntV Infographic syntax docs + structure registry (`relation-dagre-flow`) -->

Source: SKILL.md on GitHub

Skill behaviors

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.

Third-party checks

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

Provenance

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

Capability

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