c4-container
Document C4 Container Architecture
Container architecture documentation can become inconsistent when components, APIs, and deployment units are tracked separately. This skill helps Claude, Codex, and Claude Code synthesize components into C4 container documents, diagrams, and API summaries.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "c4-container" from https://skillstore.io/skills/sickn33-c4-container.md and its manifest at https://skillstore.io/api/skills/sickn33-c4-container/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "c4-container". A web app, API service, PostgreSQL database, and message queue with brief component notes.
Expected outcome:
- A container summary with web, API, database, and queue responsibilities.
- A dependency list that explains user, service, database, and messaging relationships.
- A Mermaid C4Container diagram outline for the deployment view.
Using "c4-container". Several component documents and a Kubernetes deployment summary for a microservice system.
Expected outcome:
- A mapped list of components inside each deployment container.
- An interface summary with REST, event, and database interactions.
- A gap list for missing scaling, resource, and ownership details.
Using "c4-container". API notes for a container that exposes public and internal endpoints.
Expected outcome:
- A container API section with protocol, purpose, endpoint groups, and consumers.
- OpenAPI specification guidance for request parameters and response descriptions.
- Dependencies and external systems that should appear on the container diagram.
Security Audit
SafeThe static findings are false positives caused by Markdown examples, diagram fences, and placeholder API documentation. No evidence of command execution, unauthorized network activity, prompt injection, or system reconnaissance intent was found in SKILL.md.
Risk Factors
⚙️ External commands (8)
🌐 Network access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-c4-container/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-c4-container?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-c4-container?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-c4-container/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-c4-container.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). c4-container security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-c4-container/audits/4BibTeX citation
@techreport{sickn33-sickn33-c4-container-2026,
author = {sickn33},
title = {c4-container security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-c4-container/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "c4-container security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sickn33-c4-container/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-c4-container:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare service documentation
Turn component notes into clear container documentation for service ownership and onboarding.
Create API architecture notes
Document container interfaces, protocols, dependencies, and API specifications before implementation review.
Review deployment boundaries
Compare containers, databases, queues, and external systems in a shared C4 model view.
Try These Prompts
Create C4 container-level documentation for this system. Use my component list, technologies, and deployment notes. Include containers, interfaces, dependencies, and a Mermaid diagram outline.
Review these component documents and group them into deployment containers. Explain each boundary, list contained components, and identify missing deployment details.
Create container interface documentation from these service notes. Include protocols, endpoints, external systems, dependencies, and OpenAPI specification guidance.
Build a complete C4 container package from these component, API, infrastructure, and deployment inputs. Include rationale, diagrams, API summaries, scaling notes, and review gaps.
Best Practices
- Provide component documents, deployment notes, and known infrastructure constraints together.
- Keep container names aligned with real deployable units and ownership boundaries.
- Review generated diagrams with engineers who operate the services.
Avoid
- Do not use it for code-level class or function documentation.
- Do not invent containers when deployment ownership is unknown.
- Do not treat placeholder OpenAPI examples as production specifications.