c4-context
Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill c4-context60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 1.34xAgent success when using this skill
Validation for skill structure
Discovery
42%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at listing specific capabilities within the C4 documentation domain, but critically lacks any 'Use when...' guidance that would help Claude know when to select this skill. The trigger terms are domain-appropriate but could benefit from more natural language variations users might employ.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks for C4 diagrams, system context documentation, architecture overviews, or needs to document how a system interacts with users and external systems.'
Include natural language variations users might say: 'architecture documentation', 'system overview diagram', 'stakeholder interactions', 'external system integrations'.
Clarify the C4 context level distinction to reduce overlap with other documentation skills, e.g., 'For Context-level (Level 1) C4 diagrams only; not for Container, Component, or Code levels.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies.' These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does well, but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Contains relevant domain terms like 'C4', 'context diagrams', 'personas', 'user journeys', but misses common variations users might say such as 'architecture diagram', 'system overview', or 'stakeholder mapping'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'C4 Context-level' qualifier provides some specificity, but terms like 'personas', 'user journeys', and 'system features' could overlap with UX design, product management, or general documentation skills. | 2 / 3 |
Total | 8 / 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 useful C4 context diagram templates and Mermaid syntax examples, but lacks actionable workflow guidance for actually creating the documentation. The content is template-heavy with placeholders rather than concrete instructions, and the generic 'Use this skill when' boilerplate adds unnecessary tokens without value.
Suggestions
Replace the vague Instructions section with a concrete numbered workflow: 1) Gather system info, 2) Identify personas, 3) Map features to personas, 4) Document external dependencies, 5) Create diagram, 6) Validate with stakeholders
Add validation checkpoints such as 'Verify all external systems are documented by checking API integrations and configuration files'
Remove or condense the generic 'Use this skill when/Do not use' boilerplate - it adds no C4-specific value
Provide at least one concrete filled-in example (e.g., an e-commerce system) rather than only placeholder templates
| 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 good Mermaid diagram template with executable syntax, but most content is template placeholders ([Persona Name], [Description]) rather than concrete guidance. The instructions section is vague ('Apply relevant best practices') rather than specific. | 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 is complete and accurate. | 1 / 3 |
Progressive Disclosure | References implementation-playbook.md and related documentation (Container/Component docs), but the main content is a mix of templates and guidance that could be better organized. The structure exists but content placement is inconsistent. | 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.