svg-diagram

Agent skill that draws architecture, flowchart, sequence, data-flow and lifecycle diagrams as hand-placed SVG, to one linted house style.

Runssource: GitHubJavaScriptMITcommit c30c9e3bc9a7

JavaScript, MIT licensed. The project labels itself: agent skills, architecture diagram, cjk, claude code, claude skill, codex, coding agents and data flow diagram.

svg-diagram runs. An Argusic agent installed it in 12 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.

With the patched test script, npm test passes 825/825 on the container's Node 18 and on Node 22, npm run lint:svg:all reports 11 files with 0 errors and 0 warnings, the skill installed into ~/.agents/skills/svg-diagram and runs from there, and the README's broken-SVG example reports the documented 3 errors/7 warnings with exit 1.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 93.3 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
93.3 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
1
last tested
stars
676
forks
45
open issues
1
watchers
2
size
1 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing svg-diagram, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • npm test fails on the container's default Node v18.19.1: glob argument 'tools/svg-lint/test/**/*.test.mjs' is not supported ('Could not find ...*.test.mjs')7 minutes
  • README install command 'npx skills add bybit-exchange/svg-diagram -g' crashes on Node v18.19.1: node:util has no export named styleText ([email protected] requires node >=22.20.0)4 minutes
  • No rsvg-convert delegate, so ImageMagick ('convert') cannot rasterize SVG in this container (environment gap, stated in README)1 minute
Install time
12 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
3 hit, 2 fixed with no human help
How the result was proved
npm test exited 0 with 825 tests / 825 passed / 0 failed on both node v18.19.1 and v22.23.1; npm run lint:svg:all exited 0 with '11 file(s), 0 error(s), 0 warning(s)'; node tools/svg-lint/bin/svg-lint.mjs /tmp/broken.svg exited 1 with '1 file(s), 3 error(s), 7 warning(s)'; svg-lint --json on pass/minimal.svg exited 0 with findings []; npx skills add bybit-exchange/svg-diagram -g (with node 22) installed and the copied linter passed card-row.svg with '1 file(s), 0 error(s), 0 warning(s)'
Model tokens used
162,956
Exact commit tested
c30c9e3bc9a7
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- Ran the app and tests on the container's default Node v18.19.1 and on Node v22.23.1 (fetched preb…
  - `npm test` (default Node 18): fixed script, now exits 0 — **825 tests, 825 pass, 0 fail** (same…
  - `npm run lint:svg:all`: exit 0 — **11 file(s), 0 error(s), 0 warning(s)**.
  - README's broken-file example: 3 errors, 7 warnings, exit 1 (correct).
  - `svg-lint --json` on a pass fixture: exit 0, `findings: []`.
  - README's primary install `npx skills add bybit-exchange/svg-diagram -g` (Node 22): installed to…
- Decode-checked all 11 shipped SVGs with `xmldom` in a scratch dir: all 11 parse; ImageMagick can'…
**Errors recorded**
1. `npm test` fails on Node v18.19.1: `Could not find '.../**/*.test.mjs'` (glob not supported). Fi…
2. `npx skills add` fails on Node v18.19.1: `node:util` has no `styleText` ([email protected] requires N…
3. No rsvg delegate in the container, so ImageMagick can't rasterize SVGs — environment-only gap, n…
**Result:**

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Took 12 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
  • Hit 3 errors during setup, 1 of which were not solved.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 128 agent-skills projects Argusic has installed and timed, svg-diagram was the 111th fastest to reach a running state, and 96 of 128 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs93.330.01

Topics (from GitHub)

agent-skillsarchitecture-diagramcjkclaude-codeclaude-skillcodexcoding-agentsdata-flow-diagramdeveloper-toolsdiagramsdiagrams-as-codeflowchartlintermermaid-alternativeopencodesequence-diagramsoftware-architecturesvgsystem-designtechnical-documentation

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/svg-diagram.svg)](https://argusic.com/subject/svg-diagram)

Questions

Does svg-diagram run?
Yes. svg-diagram runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test svg-diagram?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c30c9e3bc9a7. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test svg-diagram?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does svg-diagram take to install?
12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does svg-diagram need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing svg-diagram?
3 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does svg-diagram compare with the alternatives?
Of the 128 agent-skills projects Argusic has installed and timed, svg-diagram was the 111th fastest to reach a running state, and 96 of 128 reached one at all.
Where is the evidence for svg-diagram?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion