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.

examplesknowledge-and-outlinecapability-relationship-map.md

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

Central Concept Map — Capability Relationships (Infographic)

Best for: a small hub-and-spoke relationship picture where one central concept connects to a handful of related capabilities Avoid when: the graph is dense, highly directional, or needs weighted edges and algorithmic layout control Answers: what sits at the center, and which surrounding ideas or services relate to it

infographic relation-circle-icon-badge
theme
  colorPrimary #2b66c4
  palette
    - #2b66c4
    - #2f9e44
    - #f3a33c
    - #d1242f
    - #7048e8
    - #0f9b9b
    - #c16f8a
    - #7c5a3d
data
  title Capability Relationship Map
  desc Badges count the relations each node carries
  nodes
    - id core
      label Platform Core
      group central
      value 5
    - id identity
      label Identity
      group support
      value 1
    - id billing
      label Billing
      group support
      value 1
    - id search
      label Search
      group support
      value 1
    - id analytics
      label Analytics
      group support
      value 1
    - id security
      label Security
      group support
      value 1
  relations
    - from core
      to identity
    - from core
      to billing
    - from core
      to search
    - from core
      to analytics
    - from core
      to security

Data Shape

Use nodes and relations when you have one center and a few simple surrounding connections. ⚠️ The icon-badge item prints a number on every node: without a value it reads 0, so give each node the count the figure is about (here, how many relations it carries — 5 for the hub, 1 per satellite).

Key Options

Option Effect
relation-circle-icon-badge Hub-and-spoke relation treatment, with a count badge per node
value 5 The badge number; the item prints it unconditionally
nodes Declares the entities shown in the map
relations Declares which entities connect. Relation labels are not drawn by this structure — the desc has to carry that information
group Lets the template distinguish the central node from its satellites

Pitfalls

  • ❌ Large dependency webs → ✅ this family is best for a small conceptual relation map
  • ❌ Treating it like a precise architecture graph → ✅ use a rectangle graph when layout control matters
  • ❌ Omitting stable node IDs → ✅ relations should bind to IDs, not only labels
  • ❌ Relying on relations[].label → ✅ the circle and network structures draw no edge labels; if the words on the arrows are the point, use a sequence-* template

Alternatives

Variant Use instead
Directed service dependency graph service-dependency-network.md
Explicit network or architecture topology PlantUML or ECharts graph examples
Hierarchical tree platform-org-structure.md
<!-- source: AntV Infographic template reference (`relation-circle-icon-badge`) + syntax docs for nodes/relations -->

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