Archify
Archify combines an agent Skill with a Node.js diagram pipeline. The Skill guides input authoring; the renderer consumes structured JSON and produces an interactive HTML artifact. We tested the published 3.2.0 archive directly rather than a same-name npm package or a global agent installation. The listed Cursor installer is an upstream documented setup path, separate from our fixed-archive reproduction.
The recorded suite made 18 CLI invocations using a supplied six-node, five-edge Chinese workflow, plus 11 independent Chrome conditions. Selected structural, layout, required-edge, path and malformed-input cases were rejected without changing the prior HTML. A copied HTML worked offline; finder, focus, reach, directed routes and actual SVG/PNG downloads carried the expected supplied content.
Acceptance needs more than file existence. Ordinary artifact checking accepted missing delivery provenance as unknown unless strict mode was requested. With a deliberately unavailable browser, finalize returned exit 2 and a skipped browser gate after valid HTML had already replaced the target. The narrow page stayed within 390 pixels but clipped right-hand diagram nodes. These results do not establish natural-language accuracy, large-graph readability or other diagram modes.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-08
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 10
- Latest release
- archify-dsh-v1.1.0 (2026-11-08)
- Open issues
- 358
- Recent issues with at least one comment
- 1/5
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Who it fits
- You want reviewable diagram JSON, explicit topology contracts and an offline desktop HTML handoff.
- You can inspect each gate and promote a separate candidate only after full acceptance.
- You expect validated labels and arrows to independently prove business or repository truth.
- You need already verified large graphs, other diagram modes or a complete narrow-screen reading experience.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!