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.
62
Quality
57%
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 ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/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
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable template structure for C4 Context documentation with a good Mermaid diagram example, but lacks actionable workflow guidance. The content is template-heavy with placeholders rather than concrete instructions, and the generic boilerplate sections add little value. The skill would benefit from a clear step-by-step process for creating context documentation.
Suggestions
Replace the vague 'Instructions' section with a concrete numbered workflow: 1) Identify stakeholders, 2) Document personas, 3) Map user journeys, 4) Identify external systems, 5) Create context diagram, 6) Validate with stakeholders
Remove or condense the generic 'Use this skill when / Do not use' boilerplate sections that don't add C4-specific value
Add validation checkpoints such as 'Verify all external system integrations are documented' or 'Confirm diagram includes all personas identified'
Move the template placeholders to a separate TEMPLATE.md file and keep SKILL.md focused on the process and concrete examples
| 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 ([Feature Name], [Description]) 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 lists what outputs should exist but doesn't provide steps for how to create them, gather information, or validate the documentation. Missing any validation checkpoints. | 1 / 3 |
Progressive Disclosure | References an external resource (resources/implementation-playbook.md) and links to related C4 documentation, but the main content is somewhat monolithic with templates that could be separated. The structure is present but not optimally organized. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
20ba150
Table of Contents
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.