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.

examplesmigration-and-rolloutdevice-rollout-phases.md

3D Pucks — Device Rollout Phases (Infographic)

Best for: a short physical rollout plan where the stages are tangible objects, not abstract tasks Avoid when: the steps are parallel workstreams (the zigzag implies one path) or there are more than six Answers: what happens at each station of a hardware rollout, and how many devices move at each step

infographic sequence-zigzag-pucks-3d-simple
theme
  colorPrimary #2b66c4
  palette
    - #2b66c4
    - #2f9e44
    - #f3a33c
    - #d1242f
    - #7048e8
    - #0f9b9b
    - #c16f8a
    - #7c5a3d
data
  title Field Device Rollout
  desc Five stations from warehouse to handover
  sequences
    - label Stage
      desc 240 units staged in the regional warehouse
    - label Flash
      desc Firmware and tenant config written and verified
    - label Ship
      desc Couriers dispatched with per-site manifests
    - label Install
      desc On-site mounting, network join, smoke test
    - label Handover
      desc Local owner signs off on the asset record

Data Shape

sequences with one entry per station, in travel order. Each entry carries a short label (the station name) and a desc with the operational detail.

Key Options

Option Effect
sequence-zigzag-pucks-3d-simple Renders each step as a 3D puck on an alternating zigzag path
sequence-zigzag-pucks-3d-underline-text Same geometry with emphasised labels
sequence-steps-simple-illus Drops the 3D treatment; use when the steps are conceptual rather than physical
Five to six entries The zigzag needs a readable rhythm; beyond six the pucks crowd the canvas

Pitfalls

  • ❌ Using 3D pucks for abstract process steps → ✅ the object metaphor implies a physical thing moving; for logic-only flows use sequence-steps-simple-illus
  • ❌ Long desc strings → ✅ each puck has a narrow column; keep the description to one clause
  • ❌ A rollout plan where stations run in parallel → ✅ the zigzag asserts a single order
  • ❌ Pucks used for quantities → ✅ they are labels, not counts; put numbers in the desc

Alternatives

Variant Use instead
Conceptual ordered steps customer-onboarding-journey.md
Steps against a calendar data-platform-migration-waves.md
A checklist with progress facts launch-readiness-checklist.md
<!-- source: AntV Infographic template registry 0.2.20 (`sequence-zigzag-pucks-3d-simple`, structure `sequence-zigzag-pucks-3d`) -->

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