williamlimasilva/c4-context
skills/c4-context/SKILL.md
Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation with system documentation to create comprehensive context-level architecture. Use when creating the highest-level C4 system context documentation.
testing
Updated Apr 29, 2026
$ install --global
skillsauthnpx skillsauth add williamlimasilva/.copilot c4-contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 29, 2026, 1:14 PM36.6s1 file scanned
SKILL.md
- name:
- c4-context
- description:
- Expert C4 Context-level documentation specialist. Creates
- model:
- sonnet
C4 Context Level: System Context
Use this skill when
- Working on c4 context level: system context tasks or workflows
- Needing guidance, best practices, or checklists for c4 context level: system context
Do not use this skill when
- The task is unrelated to c4 context level: system context
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
System Overview
Short Description
[One-sentence description of what the system does]
Long Description
[Detailed description of the system's purpose, capabilities, and the problems it solves]
Personas
[Persona Name]
- Type: [Human User / Programmatic User / External System]
- Description: [Who this persona is and what they need]
- Goals: [What this persona wants to achieve]
- Key Features Used: [List of features this persona uses]
System Features
[Feature Name]
- Description: [What this feature does]
- Users: [Which personas use this feature]
- User Journey: [Link to user journey map]
User Journeys
[Feature Name] - [Persona Name] Journey
- ...
[External System] Integration Journey
- ...
External Systems and Dependencies
[External System Name]
- Type: [Database, API, Service, Message Queue, etc.]
- Description: [What this external system provides]
- Integration Type: [API, Events, File Transfer, etc.]
- Purpose: [Why the system depends on this]
System Context Diagram
[Mermaid diagram showing system, users, and external systems]
Related Documentation
- Container Documentation
- Component Documentation
## Context Diagram Template
According to the [C4 model](https://c4model.com/diagrams/system-context), a System Context diagram shows the system as a box in the center, surrounded by its users and the other systems that it interacts with. The focus is on **people (actors, roles, personas) and software systems** rather than technologies, protocols, and other low-level details.
Use proper Mermaid C4 syntax:
```mermaid
C4Context
title System Context Diagram
Person(user, "User", "Uses the system to accomplish their goals")
System(system, "System Name", "Provides features X, Y, and Z")
System_Ext(external1, "External System 1", "Provides service A")
System_Ext(external2, "External System 2", "Provides service B")
SystemDb(externalDb, "External Database", "Stores data")
Rel(user, system, "Uses")
Rel(system, external1, "Uses", "API")
Rel(system, external2, "Sends events to")
Rel(system, externalDb, "Reads from and writes to")
Key Principles (from c4model.com):
- Focus on people and software systems, not technologies
- Show the system boundary clearly
- Include all users (human and programmatic)
- Include all external systems the system interacts with
- Keep it stakeholder-friendly - understandable by non-technical audiences
- Avoid showing technologies, protocols, or low-level details
Example Interactions
- "Create C4 Context-level documentation for the system"
- "Identify all personas and create user journey maps for key features"
- "Document external systems and create a system context diagram"
- "Analyze system documentation and create comprehensive context documentation"
- "Map user journeys for all key features including programmatic users"
Key Distinctions
- vs C4-Container agent: Provides high-level system view; Container agent focuses on deployment architecture
- vs C4-Component agent: Focuses on system context; Component agent focuses on logical component structure
- vs C4-Code agent: Provides stakeholder-friendly overview; Code agent provides technical code details
Output Examples
When creating context documentation, provide:
- Clear system descriptions (short and long)
- Comprehensive persona documentation (human and programmatic)
- Complete feature lists with descriptions
- Detailed user journey maps for all key features
- Complete external system and dependency documentation
- Mermaid context diagram showing system, users, and external systems
- Links to container and component documentation
- Stakeholder-friendly documentation understandable by non-technical audiences
- Consistent documentation format
Related Skills
williamlimasilva/workshop-create
tools
VerifiedTrustedCommunity
Create a new workshop or use an existing directory as one. Handles two paths: (A) use an existing local directory the operator points at, or (B) create a new private GitHub repo in the signed-in account. Never creates a repo inside another repo.
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/vcpkg
development
VerifiedTrustedCommunity
Guide for setting up vcpkg in C++ projects, managing dependency versions, and cross-compiling. Covers manifest initialization, CMake and Visual Studio integration, classic-to-manifest migration, version pinning, baselines, overrides, triplets, and cross-compilation. Use when a user is working with vcpkg project setup, installation, version management, or cross-platform builds. For specialized tasks, additional references cover custom registries and overlay ports (references/registries.md), CI/CD and binary caching (references/ci.md), and troubleshooting and dependency lifecycle (references/troubleshooting.md).
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/signal-write
testing
VerifiedTrustedCommunity
Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals/ for dashboard consumption and noted in the journal for persistence.
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/markstream-install
development
VerifiedTrustedCommunity
Install and configure Markstream streaming Markdown renderers for Vue, React, Svelte, Angular, Nuxt, and Vue 2 applications. Use for package selection, minimal peer dependencies, CSS order, SSR boundaries, streaming mode, and renderer setup.
SKILL.mdUpdated Jul 22, 2026