Skills c4-architecture-c4-architecture
📦
c4-architecture-c4-architecture
Content revision r1 Safe ⚙️ External commands🌐 Network access
Create C4 Architecture Documentation
Architecture documentation often becomes incomplete as codebases grow. This skill guides Claude, Codex, or Claude Code through a C4 documentation workflow.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "c4-architecture-c4-architecture" from https://skillstore.io/skills/sickn33-c4-architecture-c4-architecture.md and its manifest at https://skillstore.io/api/skills/sickn33-c4-architecture-c4-architecture/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-architecture-c4-architecture". Document a new web application repository.
Expected outcome:
- A C4-Documentation folder with code-level pages, component summaries, container views, and a system context overview.
- Mermaid diagrams show key relationships between users, containers, components, and external systems.
Using "c4-architecture-c4-architecture". Create architecture docs for a service with APIs.
Expected outcome:
- Container documentation lists service APIs, protocols, dependencies, and deployment details.
- API specification notes describe endpoints, request models, responses, authentication, and error cases.
Security Audit
Safev4 • 7/6/2026 Open versioned report
The static hits are false positives from Markdown backticks, C4 reference links, and Mermaid diagram wording in SKILL.md. No command execution, external request behavior, prompt injection, or malicious intent was found. The skill reads repository structure and writes local documentation as expected for a C4 documentation workflow.
1
Files scanned
390
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (10)
🌐 Network access (2)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
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-architecture-c4-architecture/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-c4-architecture-c4-architecture?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-c4-architecture-c4-architecture?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-c4-architecture-c4-architecture/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-c4-architecture-c4-architecture.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-architecture-c4-architecture security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-c4-architecture-c4-architecture/audits/4BibTeX citation
@techreport{sickn33-sickn33-c4-architecture-c4-architecture-2026,
author = {sickn33},
title = {c4-architecture-c4-architecture security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-c4-architecture-c4-architecture/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-architecture-c4-architecture 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-architecture-c4-architecture/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-c4-architecture-c4-architecture:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance
What You Can Build
Onboard Developers
Create a navigable C4 documentation set so new contributors can understand code structure and dependencies.
Prepare Architecture Reviews
Map components, containers, and external systems before a design review or modernization effort.
Document Service Interfaces
Identify container interfaces and prepare OpenAPI outlines for service consumers.
Try These Prompts
Generate Default C4 Docs
Create C4 documentation for this repository. Use the default C4-Documentation output folder and include code, component, container, and context levels.
Focus On Selected Folders
Analyze the src and services directories only. Exclude tests and generated files. Produce component and container documentation with Mermaid diagrams.
Map Microservice Architecture
Generate C4 documentation for a microservice repo. Emphasize deployment units, APIs, external dependencies, and OpenAPI outlines for each container.
Audit Existing C4 Output
Review existing C4-Documentation output, find gaps against the repository, and update missing relationships, personas, APIs, and diagram links.
Best Practices
- Run it after dependencies and project structure are available.
- Review generated boundaries with engineers who own the system.
- Keep generated documentation with source control changes when architecture changes.
Avoid
- Do not run it on unrelated repositories or partial file exports.
- Do not publish generated architecture docs without checking private system details.
- Do not treat generated API specs as canonical without endpoint validation.
Frequently Asked Questions
Does this skill create all four C4 levels?
Yes. It guides code, component, container, and context documentation, although teams can choose the levels they need.
Does it require external services?
No. The instructions reference C4 documentation links but do not require network calls to generate files.
Where are files written?
The workflow writes Markdown and API documentation under C4-Documentation in the repository root by default.
Can it document APIs?
Yes. It asks the assistant to identify container interfaces and prepare OpenAPI-style specifications.
Will it modify application code?
No. The described workflow creates documentation files and does not ask to change application source code.
Who should review the output?
Engineers, architects, and service owners should review diagrams, dependencies, and API descriptions for accuracy.