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.
57
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 clear capabilities and an explicit 'Use when' clause. The main weakness is reliance on technical C4 terminology that users may not naturally use when requesting this type of documentation. The description would benefit from including more natural language triggers alongside the technical terms.
Suggestions
Add natural language trigger terms users might say, such as 'architecture overview', 'system diagram', 'big picture view', or 'how the system connects to external systems'
Include file type or artifact mentions if applicable (e.g., 'context.md', 'system-context.puml') to improve trigger matching
| 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 | Specifies '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 essentially a skeleton with links to sub-skills but provides no substantive guidance on C4 context-level documentation. It lacks concrete examples, templates, or workflows for creating system context diagrams, documenting personas, or synthesizing architecture documentation. The instructions are generic placeholders that could apply to any skill.
Suggestions
Add a concrete example of a C4 context diagram with annotated elements (system, actors, external systems) showing expected output format
Define a clear workflow: e.g., 1) Identify actors → 2) Map external systems → 3) Define system boundary → 4) Document relationships → 5) Validate completeness
Replace generic instructions with C4-specific guidance: what makes a good system context description, how to identify external dependencies, persona documentation templates
Add brief descriptions to each sub-skill link explaining what it covers and when to use it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes generic boilerplate instructions ('Clarify goals, constraints, and required inputs') that don't add C4-specific value. The 'Use this skill when' section is tautological. | 2 / 3 |
Actionability | No concrete guidance on how to create C4 context diagrams, document personas, or define system boundaries. Instructions are entirely abstract ('Apply relevant best practices') with no executable examples, templates, or specific steps. | 1 / 3 |
Workflow Clarity | No workflow is defined despite the skill description mentioning synthesis of multiple documentation types. There's no sequence for creating context-level documentation, no validation steps, and no guidance on how the sub-skills connect. | 1 / 3 |
Progressive Disclosure | References to sub-skills and implementation-playbook.md exist with one-level-deep linking, but the main skill provides almost no overview content—it's essentially just a table of contents with no context on what each sub-skill does or when to use them. | 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
332e58b
- 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.