Identify deployable containers and map their interconnections for C4 diagrams.
npx skills add https://github.com/vishalkhondre/unearth --skill 04-containers
Please help me install this Agent Skill. Skill: 04-containers Source: https://github.com/vishalkhondre/unearth/tree/main/skills/04-containers Command: npx skills add https://github.com/vishalkhondre/unearth --skill 04-containers
Identifies all independently deployable units within the system boundary — the C4 "container" level. Maps how containers communicate with each other and with external systems. Detects architecture patterns that emerge from the container topology. Classifies infrastructure as internal or external. Use after 03-external-systems when you need to produce the C4 Container diagram.
Provide the container inventory and topology by analyzing upstream reconstruction outputs and existing deployment targets to produce the 04-containers results.
High-intent search queries and answers about installing and using this skill.
To identify independently deployable containers for a C4 diagram, analyze multi-project repositories to detect runtime units, deployment targets, entry points, and process startup patterns. This produces a normalized inventory including container IDs, technology, and responsibilities.
Container topology detection identifies emerging architecture patterns such as Backend-for-Frontend (BFF), API gateway, shared database, and event-driven architectures. This is achieved by mapping how independently deployable runtime units communicate with each other and external systems.
To map container relationships in a multi-project repository, analyze the system boundary to detect independently deployable units, their deployment targets, and entry points. This reveals topology patterns like API gateways or event-driven architectures for architecture documentation.
You need to map container inventory when producing a C4 Container diagram for a system with multiple deployable units. It is used after mapping external systems to classify internal versus external infrastructure and document container responsibilities.
Yes, mapping containers for diagramming requires analyzing process startup patterns and counting entry points. Detecting these deployment targets ensures an accurate normalized inventory of runtime units and their interconnections within the system boundary.
You should avoid container-level mapping if your repository does not contain multiple independently deployable units or lacks distinct deployment targets. It is specifically designed for multi-project repositories needing C4 Container diagram documentation.
ConsiliencyGenerate standardized C4 architecture diagrams using Mermaid syntax.
wesleyegbertoGenerate C4 architecture documentation with Markdown outputs and Mermaid diagrams.
Dokkabei97Generate CI/CD pipeline configurations for GitHub Actions and GitLab CI.
daffy0208Create interactive Three.js and React Three Fiber 3D visualizations with lighting and camera controls.
