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-roleschord-team-handoffs.md

Chord — Cross-Team Handoffs (ECharts)

Best for: showing bidirectional relationship strength between a small set of peer groups Avoid when: the flow is directional by stage or needs an explicit process sequence (use sankey or lines) Answers: which groups exchange the most work, where the strongest pairings sit, and which groups are relatively isolated

{
  "color": ["#2b66c4", "#2f9e44", "#f3a33c", "#d1242f", "#7048e8", "#0f9b9b", "#c16f8a", "#7c5a3d"],
  "width": 860,
  "height": 420,
  "title": { "text": "Cross-Team Handoffs", "subtext": "Weekly ticket transfer volume", "left": "left" },
  "series": [
    {
      "type": "chord",
      "radius": ["34%", "68%"],
      "center": ["50%", "58%"],
      "clockwise": false,
      "sort": "descending",
      "sortSub": "descending",
      "label": { "show": true, "fontSize": 11 },
      "lineStyle": { "color": "target", "opacity": 0.55, "width": 1 },
      "data": [
        { "name": "Core" },
        { "name": "Billing" },
        { "name": "Support" },
        { "name": "Identity" },
        { "name": "Data" }
      ],
      "links": [
        { "source": "Core", "target": "Billing", "value": 32 },
        { "source": "Core", "target": "Support", "value": 24 },
        { "source": "Core", "target": "Identity", "value": 18 },
        { "source": "Core", "target": "Data", "value": 12 },
        { "source": "Billing", "target": "Support", "value": 16 },
        { "source": "Billing", "target": "Data", "value": 14 },
        { "source": "Support", "target": "Identity", "value": 10 },
        { "source": "Support", "target": "Data", "value": 12 },
        { "source": "Identity", "target": "Data", "value": 6 }
      ]
    }
  ]
}

Key Options

Option Effect
series.type: "chord" Encodes pairwise relationship strength in a circular matrix form
links Supplies the relationship list directly, which is the simpler official pattern
sort / sortSub Keeps the strongest arcs grouped more readably
radius / center Reserves enough whitespace for labels around the ring
lineStyle.opacity Prevents dense ribbons from turning into a solid blob

Data Shape

One data array naming each group, plus links[{ source, target, value }] describing the strongest relationships between them.

Pitfalls

  • ❌ Too many entities → ✅ chord diagrams saturate quickly; keep the set small
  • ❌ Treating the matrix as directional stages → ✅ chord is about peer-to-peer strength, not sequence
  • ❌ Mixing weak incidental links with the main structure → ✅ aggregate or drop minor ribbons so the ring stays readable
  • ❌ Weak relationships left unaggregated → ✅ tiny ribbons clutter the ring and add little value

Alternatives

Variant Use instead
Directional staged flow sankey-channel-to-fulfilment.md
Fixed-path links on a plane lines-route-flows.md
General dependency network graph-platform-dependencies.md
<!-- source: ECharts option manual (series-chord) + v6 chord examples -->

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