c4-context
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.
54
Quality
49%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/c4-context/SKILL.mdQuality
Discovery
77%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured description with strong specificity and completeness, including an explicit 'Use when' clause. The main weakness is reliance on technical C4 terminology that users unfamiliar with the framework might not use, and moderate overlap risk with other architecture documentation skills.
Suggestions
Add natural language trigger terms users might say, such as 'architecture overview', 'system diagram', 'how systems interact', or 'big picture view'
Strengthen distinctiveness by explicitly contrasting with other C4 levels, e.g., 'Use for context-level (not container or component level) C4 documentation'
| 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 systems connect', 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 'highest-level' helps but 'system documentation' is somewhat generic. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a skeleton/template with minimal actual content. It lacks any concrete guidance on creating C4 context diagrams, documenting personas, user journeys, or external dependencies. The structure suggests progressive disclosure but the main skill provides no actionable value on its own.
Suggestions
Add concrete examples of C4 context diagram creation, including sample PlantUML or Structurizr DSL code for system context views
Provide a clear workflow with numbered steps for documenting system context: e.g., 1) Identify system boundaries, 2) Document personas, 3) Map external systems, 4) Validate completeness
Fill in the 'System Overview' section with actual guidance on what constitutes good context-level documentation
Replace generic instructions ('Apply relevant best practices') with specific, actionable guidance for C4 context documentation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes generic boilerplate sections ('Use this skill when', 'Do not use this skill when') that add little value. The instructions are vague placeholders rather than domain-specific guidance. | 2 / 3 |
Actionability | The skill provides no concrete, executable guidance. Instructions like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices' are abstract and non-actionable. No examples, code, or specific steps for creating C4 context diagrams are provided. | 1 / 3 |
Workflow Clarity | There is no clear workflow or sequence for creating C4 context-level documentation. The instructions are generic bullet points without any process flow, validation steps, or checkpoints for the complex task of system context documentation. | 1 / 3 |
Progressive Disclosure | The skill does reference sub-skills and an implementation playbook, showing some structure. However, the main content is essentially empty, providing no overview or context before directing to other files. The 'System Overview' section is blank. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.