excalidash-c4-container

Generates C4 Level 2 container diagrams of one software system via Excalidraw MCP tools.

2|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/gabedsam01/excalidash-v2 --skill excalidash-c4-container-gabedsam01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: excalidash-c4-container
Source: https://github.com/gabedsam01/excalidash-v2/tree/main/skills/excalidash/excalidash-c4-container
Command: npx skills add https://github.com/gabedsam01/excalidash-v2 --skill excalidash-c4-container-gabedsam01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Drawing a correct C4 Level 2 container diagram by hand is slow and error-prone: containers spill outside the system boundary, arrows cross labels, datastores look like plain boxes, and connection strings leak into exported images. This Skill automates the full build-and-quality loop so the diagram scores at least 95 with zero hard blockers. ## Core Features & Use Cases - Boundary-correct generation: Creates exactly one system-boundary frame holding typed containers (apps, APIs, queues, datastores) with actors and external systems placed outside it. - Mandatory quality loop: Runs lint, score, repair, polish, and architecture validation until the drawing reaches score >= 95 with no hard blockers, with rollback to saved checkpoints on regression. - Secret redaction: Redacts database URLs, broker credentials, API keys, and tokens before any tool call and re-scans the exported SVG/PNG. - Use Case: Ask to zoom into an existing C4 context diagram of your billing platform; the Skill converts it into a container view showing the React SPA, Spring Boot API, PostgreSQL, Redis, and Kafka with protocol-labeled edges. ## Quick Start Ask the assistant to draw a C4 Level 2 container diagram of one named system, listing its apps, APIs, datastores, queues, actors, and external systems with the protocol used on each connection.

Frequently Asked Questions about excalidash-c4-container

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a C4 container diagram with Excalidraw MCP?

Describe one system with its containers, technologies, actors, external systems, and per-edge protocols, then the Skill calls one create path such as create_diagram_from_prompt or convert_diagram_type. It then places icons, runs the lint-score-repair loop, validates the architecture, and exports the drawing.

What is the difference between a C4 context and container diagram?

A context diagram (Level 1) shows one system as a single box with its actors and external integrations. A container diagram (Level 2) zooms inside that box to show runnable containers like web apps, APIs, databases, and queues, and this Skill can convert an existing context drawing into one.

Can I expand an existing C4 context diagram into containers?

Yes. Pass the existing context drawing's structure to convert_diagram_type with targetType c4_container, and the central system expands into its containers inside a generated boundary frame while actors and external systems stay outside.

When should I not use a C4 container diagram?

Avoid it when the audience only needs scope and integrations (use a C4 context diagram), when drilling into classes or modules of one container (use a C4 component diagram), when showing time-ordered messages (use a sequence diagram), or when more than one system's internals are in scope.

How are database credentials handled in generated diagrams?

Connection strings, broker credentials, API keys, and tokens are redacted into typed placeholders like [REDACTED_DATABASE_URL] before any tool call. The exported SVG or PNG is re-scanned afterward as a backstop so no live secret appears in the drawing.

Why does my container diagram fail validation?

Common causes are containers clipped by the boundary frame, arrows crossing labels, external systems drawn inside the boundary, or Level-3 components leaking in. The repair_drawing loop fixes these until the score reaches 95 and hard blockers are empty.