c4-context

Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies.

Quality

58%

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

50%

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

The skill provides a usable Mermaid template and a logical documentation scaffold, but it mixes vague instructional filler with bracket placeholders and points to a non-existent reference file. Tightening the guidance and fixing or removing the broken reference would materially improve it.

Suggestions

Create the referenced resources/implementation-playbook.md (or remove the dead link) so the progressive-disclosure pointer resolves.

Replace the generic Instructions ('Apply relevant best practices and validate outcomes') with concrete, ordered steps with explicit validation/verification checkpoints.

Trim the explanatory prose about what a C4 context diagram is and the restated Key Principles, since Claude already knows the C4 model.

Fix the stray/unclosed code fence after the 'Related Documentation' list, which breaks the markdown structure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but spends tokens explaining what a C4 context diagram is ('According to the C4 model...') and restating principles Claude already knows, keeping it short of the lean level-3 bar.	2 / 3
Actionability	The Mermaid C4Context block is concrete and copy-paste ready, but the surrounding Instructions are abstract ('Clarify goals...', 'Apply relevant best practices and validate outcomes') and the bulk is bracketed template scaffolding rather than executable guidance.	2 / 3
Workflow Clarity	A documentation-generation sequence is implied (Overview → Personas → Features → Journeys → External Systems → Diagram), but there are no explicit validation checkpoints or feedback loops and the 'Instructions' steps remain generic.	2 / 3
Progressive Disclosure	Sections are organized and the body signals one external reference ('open resources/implementation-playbook.md'), but that file does not exist in the bundle, so the single one-level-deep pointer is broken rather than a clean progressive split.	2 / 3
	Total	8 / 12 Passed

Description

67%

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 clearly conveys what the skill does with concrete actions and a distinct C4-context niche, but it lacks an explicit trigger ('Use when...') clause and leans on slightly technical role phrasing. Adding natural-language trigger conditions would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrases (e.g., 'Use when creating a system context diagram, documenting personas, or mapping external dependencies').

Replace the 'Expert ... specialist' role lead with direct third-person action verbs to remove jargon and improve trigger-term naturalness.

Include common user variations such as 'C4 context diagram', 'system context', or 'user journey maps' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies' — matching the level-3 anchor of several specific actions rather than the level-2 single-domain example.	3 / 3
Completeness	Clearly states what the skill does but provides no explicit 'when' guidance; per the rubric, a missing 'Use when...' clause caps completeness at 2 even though the 'what' is well covered.	2 / 3
Trigger Term Quality	Contains relevant domain terms (system context diagrams, personas, user journeys) but leads with the jargon-ish role phrase 'C4 Context-level documentation specialist' and omits common natural variations a user might say, falling short of level-3 keyword coverage.	2 / 3
Distinctiveness Conflict Risk	The C4 Context-level framing carves a clear niche distinct from Container/Component/Code skills, with triggers unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/c4-context/SKILL.md
Commit: a3068b7

Reviewed: about 14 hours 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.