docu.md skillsSAFE

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

npx skills add markdown-viewer/skills

cp -r skills/documd-visuals ~/.claude/skills/

skills/
├── documd-visuals/        ← the skill package — the only skill here, and the only thing installed
│   ├── SKILL.md           ← router: iron rules, 31 goals, capability boundaries
│   ├── converting.md      ← the documd CLI: install, formats, flags, what survives an export
│   ├── catalog/           ← every scenario: domain, engines, tier, example files
│   ├── goals/             ← one guide per goal domain
│   ├── engines/           ← per-engine reference + coverage/ ledgers (units, then examples by

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: documd-visuals
license: CC-BY-4.0
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`.
description: >
  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.
---

# documd visuals

Routing for every diagram, chart, card and layout this document pipeline can render.

**Figures are text, in place.** A fence (`plantuml` · `vega` · `echarts` · `infographic`) or bare HTML
written into the Markdown *is* the figure: the viewer draws it live, the block stays editable, and nothing
is pre-rendered, built or exported first. `documd` is optional — export and verification only.

## Iron rules

1. **Allowed fences** — `plantuml` / `puml` · `vega` · `vega-lite` · `echarts` · `infographic`,
   plus **bare HTML** — which is how system architecture diagrams, cards and page layouts are drawn.
2. **Nothing outside that list.** A fence the list does not name is a bug, not a lesser option —
   there is no second-tier engine.
3. **One diagram per fence.** Do not put two engines in one block, and never nest fences.
4. **HTML is bare, never ` ```html `** — a fenced block becomes an image. Start from a real file rather
   than inventing one: [`layered-with-wings.md`](examples/system-architecture/layered-with-wings.md) for a
   system, [`executive-brief-summary.md`](examples/internal-documents/executive-brief-summary.md) for a card.
5. **Inline the data.** `vega` / `vega-lite` / `echarts` must carry their own `values` / `series` data;
   external URLs are unreliable on the export path.
6. **State the reading in the copy.** Every figure answers one question — put it in the prose or the
   block's `title`.
7. **Pick a theme, then colour from it.** Colours come from one of the themes indexed in
   [`styles/palette.md`](styles/palette.md); copy that theme's block for your engine and take every
   value from it — a hex picked by hand, or two themes in one figure, is a bug. Charts pass the
   categorical ramp in order; cards use one accent plus neutrals.

## Route by goal

Find the reader's goal, open the goal guide, pick an example. Engines are suggestions; the guide and
examples are authoritative.

### A — data & metrics

| Goal | Trigger keywords | Engines | Read |
|---|---|---|---|
| service-reliability | latency · p95/p99 · SLO · SLA · error budget · burn rate · availability · uptime · reliability | echarts vega infographic | [goals/service-reliability.md](goals/service-reliability.md) |
| ops-monitoring | incident load · alert volume · outliers · anomalies · service scorecard · support volume | echarts vega infographic | [goals/ops-monitoring.md](goals/ops-monitoring.md) |
| delivery-throughput | throughput · cycle time · lead time · velocity · capacity · staffing · backlog · WIP · rank movement | echarts vega infographic | [goals/delivery-throughput.md](goals/delivery-throughput.md) |
| goal-and-status-reporting | OKR · KPI · target vs actual · goal attainment · status board · dashboard · scorecard | echarts vega infographic html-css | [goals/goal-and-status-reporting.md](goals/goal-and-status-reporting.md) |
| product-metrics | conversion · funnel · adoption · retention · churn · activation · signup · cohorts · experiment | echarts infographic | [goals/product-metrics.md](goals/product-metrics.md) |
| business-reporting | quarterly results · revenue · ARR · revenue mix · margin · periodic results · forecast | infographic vega echarts | [goals/business-reporting.md](goals/business-reporting.md) |
| go-to-market | pipeline · channel · partner · partner tiers · market entry · sales funnel · SWOT · campaigns | echarts infographic | [goals/go-to-market.md](goals/go-to-market.md) |
| cost-and-budget | cost · spend · budget · cloud bill · savings · cost reduction · capex · unit economics | echarts infographic vega | [goals/cost-and-budget.md](goals/cost-and-budget.md) |
| data-exploration | correlation · distribution · regression · outlier detection · missing data · small multiples · density | vega echarts | [goals/data-exploration.md](goals/data-exploration.md) |

### B — process & systems

| Goal | Trigger keywords | Engines | Read |
|---|---|---|---|
| engineering-operations | standup · sprint ritual · team rhythm · on-call · coverage · shift handover · deploy cadence · checklist | infographic vega echarts | [goals/engineering-operations.md](goals/engineering-operations.md) |
| incident-management | incident · postmortem · escalation · triage · runbook · change request · launch readiness · review | infographic echarts html-css | [goals/incident-management.md](goals/incident-management.md) |
| process-and-workflow | approval · workflow · swimlane · SOP · process map · BPMN · gate · procurement | plantuml infographic | [goals/process-and-workflow.md](goals/process-and-workflow.md) |
| software-design | class · do

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

declared (11 observation(s))

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (7)

console.log(`\n${violations.length} use(s) a token does not allow:`);

const rel = `../../examples/${domain}/${name}.md`;

const rel = `../../goals/${domain}.md`;

md.push(`### [${domain}](../../goals/${domain}.md)`, '');

.map((e) => `[${path.basename(e.file)}](../../${e.file})`)

'- Catalog: [`../../catalog/scenarios.md`](../../catalog/scenarios.md)',

<div class="card-policy-panel"><p class="card-policy-label">Applies To</p><p class="card-policy-text">Production service accounts, CI/CD deploy identities, partner integration secrets, and database ac

Gates applied: no_behavioural_pass.

[![ModelsAtlas audit: docu.md skills](https://modelsatlas.com/skills/markdown-viewer/archimate/badge.svg)](https://modelsatlas.com/skills/markdown-viewer/archimate/)

Not your listing, or something out of date? Claim or update your listing.