CtrlK
BlogDocsLog inGet started
Tessl Logo

archify

Validated interactive HTML diagrams, upstream-maintained.

44

Quality

49%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/creative/archify/SKILL.md
SKILL.md
Quality
Evals
Security

Archify (upstream-maintained)

Catalog stub. This entry is maintained upstream at tt-a1i/archify: the project ships a self-contained skill directory (archify/) with the Node CLI, schemas, renderers, examples and references. hermes skills install official/creative/archify pulls the current tree live from that repo (quarantined and scanned like any hub install) — this directory holds only the catalog metadata, so the vendored copy can never go stale.

Archify turns a small typed JSON spec into a self-contained, explorable HTML diagram: architecture, workflow, sequence, dataflow and lifecycle (state machine) types, dark/light themes, pan/zoom, search, relationship tracing, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. It accepts plain-language requirements or pasted Mermaid (flowchart, sequenceDiagram, stateDiagram) and can read repository evidence when the diagram must reflect real code. Every candidate goes through a 9-check validate / deliver receipt, so the output is verifiable rather than eyeballed.

Prerequisites

  • Node.js 18+ on PATH (node bin/archify.mjs doctor confirms the install; no npm install is needed inside the skill package).
  • Installs pull ~200 files (~8 MB, mostly upstream tests and examples) from GitHub; the fetch is pinned to one tree SHA, recorded in the bundle metadata.
  • Upstream's "Update awareness" step runs scripts/check-update.mjs, which reads a release manifest from GitHub and only prints a notice — it never downloads or installs anything. Skip it if outbound calls are unwanted.

After install, the bundled architecture-diagram skill remains the zero-dependency fallback (it ports the same Cocoon AI lineage archify grew out of); prefer archify when the user wants validated receipts, Mermaid conversion, sequence/lifecycle types, or export beyond a single HTML file.

Full documentation: https://github.com/tt-a1i/archify#readme

Repository
NousResearch/hermes-agent
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.