c4-context
Create C4 Context Architecture Docs
Teams need a clear system overview before discussing lower-level architecture. This skill produces C4 context documentation with personas, journeys, dependencies, and Mermaid diagrams.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "c4-context" from https://skillstore.io/skills/sickn33-c4-context.md and its manifest at https://skillstore.io/api/skills/sickn33-c4-context/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-context". Create context documentation for a customer billing portal.
Expected outcome:
A stakeholder-facing document with a system description, billing personas, payment journeys, external payment services, and a Mermaid context diagram.
Using "c4-context". Identify external systems for a support ticket platform.
Expected outcome:
- Identity provider for authentication and user roles.
- Email service for notifications and inbound ticket creation.
- Customer database for account and entitlement data.
Using "c4-context". Review a draft C4 Context document for executive readability.
Expected outcome:
A concise review that flags missing personas, unclear system boundaries, excess implementation detail, and weak dependency descriptions.
Security Audit
SafeAll ten static findings were false positives from markdown formatting, C4 diagram examples, and documentation links. The skill contains no executable code, shell invocation, data collection intent, or prompt injection evidence in SKILL.md.
Risk Factors
⚙️ External commands (3)
🌐 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-context/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-c4-context?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-c4-context?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-c4-context/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-c4-context.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-context security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-c4-context/audits/4BibTeX citation
@techreport{sickn33-sickn33-c4-context-2026,
author = {sickn33},
title = {c4-context security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-c4-context/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-context 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-context/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-c4-context:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan stakeholder architecture reviews
Create a shared system overview before deeper technical discussions.
Document product-facing user journeys
Map personas, goals, features, and journey steps for a product system.
Prepare onboarding architecture notes
Summarize system boundaries, external systems, and key interactions for new engineers.
Try These Prompts
Create C4 Context documentation for [system]. Include a short description, main users, external systems, and a Mermaid context diagram.
Build a C4 Context document for [system]. Identify personas, key features, user goals, and journey steps for each major feature.
Use the provided container, component, and product notes to create a C4 Context document for [system]. Highlight boundaries and dependencies.
Review this C4 Context documentation for clarity, missing personas, missing external systems, and stakeholder readability. Suggest concrete improvements.
Best Practices
- Start with business goals, primary users, and the system boundary.
- Keep diagrams focused on people, software systems, and external dependencies.
- Link context documentation to deeper container and component views.
Avoid
- Do not include deployment details in a context-level diagram.
- Do not omit programmatic users or external service consumers.
- Do not create diagrams before confirming system scope and audience.