How do I install the Architecture Viewer skill?

Run npx skillmds@latest add jakeselby/architecture-viewer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Architecture Viewer safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Architecture Viewer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Architecture Viewer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Architecture Viewer?

JakeSelby (@jakeselby) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Architecture Viewer by jakeselby — Agent Skill

Name: Architecture Viewer
Rating: 4.666666666666667 (3 reviews)
Author: JakeSelby

Architecture Viewer

Open or update an architecture diagram with the selected builtin or custom viewer, and preserve a neutral session handoff. Use when the user asks to inspect architecture interactively or continue an existing diagram session.

JakeSelby Updated Sep 22, 2026

File contents

Architecture viewer

Inspect selection with harness integrations show architecture-viewer --json. Use an explicit invocation override only when requested. Report unavailable implementations; never silently change the selection or install an alternative.
Run harness integrations doctor architecture-viewer to obtain the selected adapter's actual capabilities. Missing required capabilities are errors, not evidence that a different viewer was selected.
Prepare an authorized immutable snapshot. For the upstream adapter use architecture-diagram profile 1, an explicit project root, optional source/metrics roots, and the SHA-256 of the exact profile bytes. Keep the profile and roots inside that project unless the user pre-authorized an additional adapter root. Preserve missing observations; report projection omissions.
Validate with harness viewer validate --input INPUT_JSON, then invoke harness viewer open --input INPUT_JSON. Record the returned session_reference, adapter, document identity, revision, digest, actual capabilities and mapping/evidence paths.
For an update, query harness viewer status --session REFERENCE, prepare a new immutable input, then use harness viewer replace-document --session REFERENCE --input REPLACEMENT_JSON --request-id REQUEST_UUID. Include the observed expected_revision. Only an acknowledged successful result means the viewer accepted the document.
Preserve the request ID when inspecting uncertain outcomes. A timeout is not cancellation. Conflicts, stale epochs, expired claims and indeterminate generation require explicit reconciliation; do not automatically reopen or replay source-changing work.
A regeneration request belongs to the current authorized workflow owner. Claim it only with the configured consumer identity and required capability, capture source identity, run the normal source-change gates, and publish with the claimed revision. Selection and viewing do not authorize edits. A detached viewer remains useful for viewing.
Put session and evidence references in the shared task handoff. Continue using the pinned session across runtimes, establishing native permissions anew. Close with harness viewer close --session REFERENCE when the user is finished.

The complete configuration, adapter envelope, profile mapping and limitations are documented in docs/viewer-integrations.md in the harness checkout. Runtime bindings share this procedure; viewer selection is independent of model/provider selection.

---name: architecture-viewerdescription: Open or update an architecture diagram with the selected builtin or custom viewer, and preserve a neutral session handoff. Use when the user asks to inspect architecture interactively or continue an existing diagram session.---# Architecture viewer1. Inspect selection with harness integrations show architecture-viewer --json. Use an explicit invocation override only when requested. Report unavailable implementations; never silently change the selection or install an alternative.2. Run harness integrations doctor architecture-viewer to obtain the selected adapter's actual capabilities. Missing required capabilities are errors, not evidence that a different viewer was selected.3. Prepare an authorized immutable snapshot. For the upstream adapter use architecture-diagram profile 1, an explicit project root, optional source/metrics roots, and the SHA-256 of the exact profile bytes. Keep the profile and roots inside that project unless the user pre-authorized an additional adapter root. Preserve missing observations; report projection omissions.4. Validate with harness viewer validate --input INPUT_JSON, then invoke harness viewer open --input INPUT_JSON. Record the returned session_reference, adapter, document identity, revision, digest, actual capabilities and mapping/evidence paths.5. For an update, query harness viewer status --session REFERENCE, prepare a new immutable input, then use harness viewer replace-document --session REFERENCE --input REPLACEMENT_JSON --request-id REQUEST_UUID. Include the observed expected_revision. Only an acknowledged successful result means the viewer accepted the document.6. Preserve the request ID when inspecting uncertain outcomes. A timeout is not cancellation. Conflicts, stale epochs, expired claims and indeterminate generation require explicit reconciliation; do not automatically reopen or replay source-changing work.7. A regeneration request belongs to the current authorized workflow owner. Claim it only with the configured consumer identity and required capability, capture source identity, run the normal source-change gates, and publish with the claimed revision. Selection and viewing do not authorize edits. A detached viewer remains useful for viewing.8. Put session and evidence references in the shared task handoff. Continue using the pinned session across runtimes, establishing native permissions anew. Close with harness viewer close --session REFERENCE when the user is finished.The complete configuration, adapter envelope, profile mapping and limitations are documented indocs/viewer-integrations.md in the harness checkout. Runtime bindings share this procedure;viewer selection is independent of model/provider selection.

Frequently asked questions