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-relationsplatform-dependency-graph.md

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

Platform Dependency Graph — Services With Icon Nodes (Infographic)

Best for: a topology view where services are recognisable by icon rather than name alone Avoid when: an acyclic flow with conditions is needed (use the dagre layout) Answers: which services talk to which, and where the shared foundations sit

infographic relation-network-icon-badge
theme
  colorPrimary #2b66c4
  palette
    - #2b66c4
    - #2f9e44
    - #f3a33c
    - #d1242f
    - #7048e8
    - #0f9b9b
    - #c16f8a
    - #7c5a3d
data
  title Service Dependencies — Core Platform
  desc Badges number the dependency depth from the gateway
  nodes
    - id gateway
      label API Gateway
      icon mdi/door-open
      value 1
    - id auth
      label Identity
      icon mdi/shield-account
      value 2
    - id events
      label Event Bus
      icon mdi/source-branch
      value 3
    - id warehouse
      label Warehouse
      icon mdi/database
      value 4
    - id billing
      label Billing
      icon mdi/receipt-text
      value 2
  relations
    - from gateway
      to auth
    - from gateway
      to billing
    - from billing
      to events
    - from events
      to warehouse

Data Shape

nodes with id, label, icon and a numeric value; relations as plain edges (this layout does not label edges well — put the protocol in the surrounding text). ⚠️ The badge is drawn for every node, so a node without a value shows a 0 — here the value is the hop count from the entry point, and the desc says so.

Key Options

Option Effect
infographic relation-network-icon-badge Icon and count badge for each service
value 2 The badge number — the item prints it unconditionally, so it must mean something
relation-network-simple-circle-node Plain circles with no badge; best when names are long (the names become tooltips, so keep the figure small)
relation-dagre-flow design block Use for directed flows with ranked ordering

Pitfalls

  • ❌ A node with no value → ✅ the badge prints 0; give it the hop count or switch template
  • ❌ Every edge labelled → ✅ this layout crowds quickly; label only the critical path
  • ❌ Icons that repeat → ✅ distinct icons make the network scannable
  • ❌ Showing all services → ✅ pick the dependency chain being discussed

Alternatives

Variant Use instead
Direct dependency chain service-dependency-network.md
Escalation with conditions incident-escalation-path.md
Capability relationships capability-relationship-map.md
<!-- source: AntV Infographic syntax docs + template list (`relation-network-icon-badge`) -->

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