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.

examplesdependencies-and-relationsservice-dependency-network.md

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

Relation Network — Service Dependencies (Infographic)

Best for: a small labeled dependency or concept network where the audience benefits from a pre-styled relational map rather than a low-level graph grammar Avoid when: the network is large, weighted, or needs algorithmic layout control (use a rectangle graph) Answers: which services depend on which others, and where the central connectors sit

infographic
theme
  colorPrimary #2b66c4
  palette
    - #2b66c4
    - #2f9e44
    - #f3a33c
    - #d1242f
    - #7048e8
    - #0f9b9b
    - #c16f8a
    - #7c5a3d
design
  structure relation-dagre-flow
  item rounded-rect-node
data
  title Service Dependency Network
  desc Core runtime dependencies around the order path, each arrow naming the call
  nodes
    - id gateway
      label Gateway
    - id auth
      label Identity
    - id catalog
      label Catalog
    - id orders
      label Orders
    - id billing
      label Billing
    - id warehouse
      label Warehouse
  relations
    - from gateway
      to auth
      label auth
    - from gateway
      to catalog
      label browse
    - from gateway
      to orders
      label checkout
    - from orders
      to billing
      label charge
    - from orders
      to warehouse
      label fulfil

Data Shape

Use nodes plus relations. Nodes should have stable id values; relations connect them with from and to, and may carry a short label.

Key Options

Option Effect
design → structure relation-dagre-flow Ranked flow layout; the only relation structure that draws the relation labels
design → item rounded-rect-node Boxes with their labels inside. simple-circle-node draws a bare circle — its label is a tooltip, so it exports as an unnamed dot
nodes Declares the entities in the network
relations Declares the connections, each with a label naming the call
Inline design block Needed because relation-dagre-flow has no built-in template name

Pitfalls

  • ❌ relation-network-simple-circle-node for a labelled map → ✅ it draws circles only: no node labels and no relation labels, so the figure is nameless. Use the inline relation-dagre-flow design
  • ❌ Treating this as a precise architecture topology → ✅ it is a high-level relation map, not a protocol diagram
  • ❌ Too many nodes → ✅ relation templates saturate quickly; keep them small and conceptual
  • ❌ Omitting stable IDs → ✅ relation edges should bind to node IDs, not only display labels

Alternatives

Variant Use instead
Rich dependency graph with layout control dependencies-and-relations/dependency-graph.md
Ordered process flow product-roadmap-sequence.md or PlantUML flow examples
Layered system structure PlantUML or HTML architecture overviews
<!-- source: AntV Infographic syntax docs (`nodes` + `relations`, inline `design` block) — relation labels verified to render only under `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