c4-context
tessl i github:sickn33/antigravity-awesome-skills --skill c4-contextExpert 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.
62%
Overall
Validation
Implementation
Activation
Validation
88%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
Implementation
38%This skill provides useful C4 context documentation templates and a good Mermaid diagram example, but lacks a clear actionable workflow for creating documentation. The content is template-heavy with placeholders rather than concrete guidance, and the instructions section is too vague to guide Claude through the documentation creation process effectively.
Suggestions
Replace the vague 'Instructions' section with a concrete numbered workflow: 1) Gather system information, 2) Identify personas, 3) Map user journeys, 4) Document external systems, 5) Create context diagram, 6) Validate completeness
Add validation checkpoints such as 'Verify all personas have at least one user journey mapped' and 'Confirm all external systems shown in diagram are documented'
Convert placeholder templates to a concrete worked example showing a real system (e.g., an e-commerce platform) to demonstrate expected output quality
Remove generic boilerplate sections ('Use this skill when' with obvious statements) to improve token efficiency
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary boilerplate (generic 'Use this skill when' sections) and template placeholders that add bulk without value. However, the C4-specific content is reasonably focused and doesn't over-explain concepts Claude would know. | 2 / 3 |
Actionability | Provides a template structure and a working Mermaid diagram example, but much of the content is placeholder text ([Persona Name], [Feature Name]) rather than executable guidance. The instructions section is vague ('Apply relevant best practices') rather than concrete. | 2 / 3 |
Workflow Clarity | No clear workflow sequence for creating C4 context documentation. The skill presents templates and examples but lacks step-by-step process with validation checkpoints. Missing guidance on how to gather information, validate completeness, or iterate on the documentation. | 1 / 3 |
Progressive Disclosure | References external resources (implementation-playbook.md, container/component docs) appropriately, but the main content is somewhat monolithic. The template sections could be split into separate reference files, with SKILL.md providing a concise overview and workflow. | 2 / 3 |
Total | 7 / 12 Passed |
Activation
77%This is a well-structured description with strong specificity and completeness, clearly listing concrete actions and including an explicit 'Use when' clause. The main weakness is trigger term quality - it relies heavily on technical C4 jargon that users may not naturally use when requesting this type of documentation. The distinctiveness could also be improved to better differentiate from other C4-level documentation skills.
Suggestions
Add natural language trigger terms users might say, such as 'architecture overview', 'system diagram', 'big picture view', 'how the system connects to external systems'
Clarify distinctiveness by explicitly stating when NOT to use this skill (e.g., 'Use this for context-level only, not for container or component details')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation with system documentation.' | 3 / 3 |
Completeness | Clearly answers both what ('Creates high-level system context diagrams, documents personas...') and when ('Use when creating the highest-level C4 system context documentation') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes domain-specific terms like 'C4', 'context diagrams', 'personas', 'user journeys', but these are technical jargon. Missing natural user phrases like 'architecture overview', 'system diagram', 'how the system fits together', or 'big picture documentation'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentions 'C4 Context-level' which distinguishes from other C4 levels (container, component), but could overlap with general architecture documentation skills. The phrase 'synthesizes container and component documentation' suggests potential confusion about when to use this vs other C4 skills. | 2 / 3 |
Total | 10 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.