c4-context

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

Quality

51%

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 skill provides a usable Mermaid template and clear section structure, but it lacks a concrete sequenced workflow with validation checkpoints, and its single progressive-disclosure reference points to a non-existent bundle file. Tightening the placeholder template and adding an explicit verification step would improve the lowest dimensions.

Suggestions

Add an explicit numbered workflow with a validation checkpoint (e.g., draft context -> verify all personas/external systems represented in diagram -> fix gaps -> finalize) to lift workflow clarity above 3.

Either create the referenced `resources/implementation-playbook.md` bundle file or remove the dangling reference, and surface it under a clearly labeled "References" section.

Condense the bracketed placeholder template and the overlapping "Output Examples" inventory to reduce repetition and tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly sectioned and skimmable, but it repeats the same documentation inventory across "System Overview", "Output Examples", and the template, and the bracketed placeholder template adds bulk that could be tightened.	3 / 5
Actionability	A concrete, copy-pasteable Mermaid C4Context example is provided, but the rest of the guidance is fill-in-the-blank placeholders ("[Persona Name]", "[Step 1]") rather than executable instruction, leaving it incomplete.	3 / 5
Workflow Clarity	The "Instructions" are four generic bullets with no sequenced workflow, and validation is only weakly implied ("validate outcomes") with no explicit validate-then-fix feedback loop for a documentation task that benefits from checkpoints.	2 / 5
Progressive Disclosure	The body references one file (`resources/implementation-playbook.md`) but no bundle directory exists, so the reference points to a missing file; the signal is buried in an Instructions bullet rather than clearly structured, and content that could be externalized is inlined.	2 / 5
	Total	10 / 20 Passed

Description

63%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 specific and well-scoped to C4 context documentation, but it omits any explicit "Use when..." trigger guidance, which caps completeness and limits natural trigger-term coverage. Adding concrete user-facing trigger phrases would raise the lower dimensions.

Suggestions

Append a "Use when creating C4 system context diagrams, documenting personas and user journeys, or mapping external system dependencies" clause to supply an explicit trigger.

Include natural synonyms and trigger phrasings users would actually say (e.g., "system context diagram", "context map", "C4 context") to broaden trigger-term coverage.

Optionally reference adjacent C4 levels by trigger to sharpen distinctiveness from the container and component skills.

Dimension	Reasoning	Score
Specificity	"Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies" lists five concrete, distinct actions with comprehensive coverage of the C4 context task.	5 / 5
Completeness	The description clearly states what the skill does but never provides a "Use when..." trigger clause, so per the rubric a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant terms like "c4 context level", "personas", and "user journeys" are present, but there are no natural synonyms or file-format triggers a user would actually say, so it sits at the "some relevant keywords, missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	"C4 Context-level" carves a clear niche distinct from container/component/code C4 skills, with only minor overlap risk among those closely related sibling skills.	4 / 5
	Total	15 / 20 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: 1f67c44

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