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.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/c4-context/SKILL.md

Quality

Content

40%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content provides a useful Mermaid example and clear C4 distinctions, but is dominated by unfilled placeholder template sections and lacks a concrete, sequenced workflow. Dangling references to non-existent sibling files further weaken its navigability and progressive disclosure.

Suggestions

Replace the generic 'Instructions' bullets with a concrete, sequenced workflow for producing context documentation (e.g., gather inputs -> identify personas -> map journeys -> draft diagram -> validate against stakeholder readability), including an explicit validation checkpoint.

Fill or remove the bracketed placeholder sections ([Persona Name], [Feature Name], etc.) so the body gives real guidance instead of empty scaffolding, or move the blank template into a separate template file the skill points to.

Resolve the dangling references to './c4-container.md' and './c4-component.md' — either ship those bundle files or relabel the links as cross-skill references so navigation is not broken.

Dimension	Reasoning	Score
Conciseness	The body avoids over-explaining concepts Claude already knows, but a large fraction is empty placeholder scaffolding ('[One-sentence description of what the system does]') that consumes tokens without adding guidance, keeping it merely efficient rather than lean.	3 / 5
Actionability	The Mermaid C4Context block and the Key Principles/Distinctions are concrete and reusable, but the core template sections are unexecuted placeholders and the 'Instructions' bullets are generic ('Apply relevant best practices and validate outcomes'), leaving the actual work under-specified.	3 / 5
Workflow Clarity	The 'Instructions' are three vague bullets with no real sequence and no validation checkpoints; the body is a sectioned template rather than a sequenced workflow, and no checkpoints or feedback loops are defined.	2 / 5
Progressive Disclosure	There are no bundle files, yet the body references './c4-container.md' and './c4-component.md' that do not exist, and the bulk of the content is inlined placeholder template rather than an overview pointing to real detailed materials.	2 / 5
	Total	10 / 20 Passed

Description

75%Weight 40%Scale 1-5

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 is well-formed: it states concrete capabilities and includes an explicit 'Use when' trigger, covering both what and when clearly. It is a solid, distinctive description that falls just short of exemplary due to slightly abstract phrasing and limited trigger synonym coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies' and 'Synthesizes container and component documentation' — but stops short of the comprehensive, fully-enumerated coverage of a 5.	4 / 5
Completeness	Explicitly answers both 'what' (creates diagrams, documents personas/journeys/features/dependencies) and 'when' ('Use when creating the highest-level C4 system context documentation'); the trigger phrase is present but could be more specific and varied for a 5.	4 / 5
Trigger Term Quality	Contains natural terms a user would say ('C4', 'system context', 'personas', 'user journeys', 'context diagrams') with good keyword coverage, but lacks synonyms and common variations that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The 'highest-level C4 system context' framing carves a clear niche distinct from container/component/code agents, though 'comprehensive context-level architecture' is broad enough to invite minor overlap with related skills.	4 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/c4-context/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.