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.

examplescustomer-and-partner-commssales-brief-card.md

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

Sales Brief Card (HTML/CSS)

Best for: a short sales-facing summary where the reader needs the positioning angle, proof point, and commercial hook in one page Avoid when: the content needs full battlecards, pricing tables, or detailed customer segmentation logic Answers: what the sales message is, and what proof or hook supports it

<div style="max-width: 900px; box-sizing: border-box; position: relative;"> <style scoped> .card-sales { background: #eef2fb; padding: 30px; font-family: 'Segoe UI', sans-serif; } .card-sales-kicker { margin: 0 0 8px; font-size: 11px; font-weight: 700; letter-spacing: 0.14em; text-transform: uppercase; color: #7c5a3d; } .card-sales-title { margin: 0 0 14px; font-size: 30px; font-weight: 700; } .card-sales-grid { display: grid; grid-template-columns: 1fr 0.9fr; gap: 14px; } .card-sales-panel { padding: 18px; background: #eef2fb; border-top: 4px solid #7c5a3d; } .card-sales-label { margin: 0 0 8px; font-size: 11px; font-weight: 700; letter-spacing: 0.12em; text-transform: uppercase; color: #7c5a3d; } .card-sales-text { margin: 0; font-size: 14px; line-height: 1.6; } .card-sales-proof { margin-top: 12px; font-size: 28px; font-weight: 700; } </style> <section class="card-sales"> <p class="card-sales-kicker">Sales Brief · Positioning</p> <h1 class="card-sales-title">Queue-First Checkout Reduces Peak-Campaign Risk</h1> <div class="card-sales-grid"> <div class="card-sales-panel"><p class="card-sales-label">Talk Track</p><p class="card-sales-text">Position the offer around operational resilience during demand spikes: shorter synchronous paths, fewer visible timeout incidents, and better release safety for high-volume campaigns.</p></div> <div class="card-sales-panel"><p class="card-sales-label">Proof Point</p><p class="card-sales-text">Observed improvement in the first high-traffic rollout window.</p><p class="card-sales-proof">-38% P95 latency</p></div> </div> </section> </div>

Data Shape

Use one positioning headline, one short sales talk-track panel, and one proof panel with a single dominant number.

Key Options

Option Effect
Sales message + proof split Separates positioning from evidence
Single dominant proof metric Gives the reader one memorable commercial hook
Warm commercial palette Fits sales/enablement tone without looking like a dashboard

Pitfalls

  • ❌ Turning the brief into a full battlecard → ✅ this should stay compact and message-first
  • ❌ Including too many proof points → ✅ one strong metric is stronger than many weak ones |
  • ❌ Using sales language with no evidence | ✅ every pitch card needs one proof anchor |

Alternatives

Variant Use instead
Partner-facing framing partner-brief-card.md
Customer outcome narrative customer-story-card.md
Metric-heavy board metric-snapshot-board.md
<!-- source: HTML/CSS inventory notes + infocard sales-room / sales-brief patterns -->

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