Skill Detail

Create interactive agent-readable diagrams with Archify

Use Archify from an agent session to turn ideas, plans, workflows, or repository structure into interactive HTML diagrams that can be explored and shared.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Security Reviewed
⭐ 77.2k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill create-interactive-agent-readable-diagrams-with-archify Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Node.js, npx, a skills-compatible agent such as Claude Code, Codex CLI, Cursor, or OpenCode
Install & setup
Install globally with npx skills add tt-a1i/archify -g, then ask your agent to use Archify to diagram an idea, plan, workflow, or repository.
Author
tt-a1i
Publisher
Individual
Last updated
Oct 4, 2026
Quick brief

Use Archify when an agent needs to produce a reviewable visual map from a prompt, plan, workflow, or codebase. The agent can invoke the installed Archify skill, generate an interactive HTML diagram, and use the output to explain architecture, trace request flows, map agent tool calls, or clarify system relationships. This belongs in the catalog as an agent-operated diagramming workflow: the scope is producing source-backed or prompt-backed interactive diagrams through an agent skill, not listing a generic diagramming library or static drawing product.

How it works

What this skill actually does

Inputs and prerequisites: Node.js, npx, a skills-compatible agent such as Claude Code, Codex CLI, Cursor, or OpenCode.

Setup notes: Install globally with npx skills add tt-a1i/archify -g , then ask your agent to use Archify to diagram an idea, plan, workflow, or repository.

Source and verification boundary: use https://tt-a1i.github.io/archify/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.