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.

examplesorganization-and-rolesteam-reporting-tree.md

Team Tree — Reporting Structure (Infographic)

Best for: a small reporting or responsibility tree where the reader needs a recognizable top-down hierarchy Avoid when: the structure is deeper than a few levels or relationships cross between branches Answers: who reports into which branch, and how the team is grouped structurally

infographic hierarchy-structure-mirror
theme
  colorPrimary #2b66c4
  palette
    - #2b66c4
    - #2f9e44
    - #f3a33c
    - #d1242f
    - #7048e8
    - #0f9b9b
    - #c16f8a
    - #7c5a3d
data
  title Team Structure
  desc Product, engineering, and operations grouped under one platform lead
  root
    label Platform Lead
    children
      - label Product
        children
          - label Growth PM
          - label Core PM
      - label Engineering
        children
          - label API Team
          - label Billing Team
      - label Operations
        children
          - label SRE
          - label Security Ops

Data Shape

Use one root with recursive children. Keep labels short and the tree shallow enough to fit cleanly.

Key Options

Option Effect
hierarchy-structure-mirror Tree layout with a more balanced mirrored presentation
root + children Recursive hierarchy data model
Short labels Preserves visual balance in the tree

Pitfalls

  • ❌ Mixing hierarchy and network semantics → ✅ use this only when parent/child structure is the point
  • ❌ Very deep organization charts → ✅ break the tree into smaller focused slices
  • ❌ Long node descriptions in every branch → ✅ keep nodes terse and use surrounding text for extra detail

Alternatives

Variant Use instead
Generic hierarchy view platform-org-structure.md
Relation network service-dependency-network.md
Rich narrative team update org-update style HTML/CSS card
<!-- source: AntV Infographic template reference (`hierarchy-structure-mirror`) + syntax docs for root/children -->

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