CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/c4-context/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A well-structured documentation-template skill with a useful executable Mermaid example and clear sectioning, but it is weighed down by generic boilerplate Instructions, placeholder-heavy guidance, and an absent validation workflow. A stray dangling code fence (line 90) also signals an editing defect.

Suggestions

Replace the generic "Instructions" block ("Apply relevant best practices and validate outcomes. Provide actionable steps and verification.") with a concrete production sequence — e.g., gather inputs → draft personas/features → map journeys → render the C4Context diagram → cross-link container/component docs — with an explicit validation step (e.g., confirm every persona and external system appears in the diagram).

Cut redundant content: the "Output Examples" section largely restates the template, and the "Use this skill when / Do not use this skill when" pair repeats the frontmatter trigger; tighten or remove these to improve conciseness.

Remove the stray dangling code fence at line 90 (an unmatched ``` after the Related Documentation list) and convert the `[placeholder]`-heavy template into either labeled guidance or a single concrete worked example so the actionable signal is clearer.

DimensionReasoningScore

Conciseness

The Mermaid example and Key Distinctions earn their place, but the generic "Instructions" block ("Apply relevant best practices and validate outcomes"), the boilerplate Use/Do-not-use sections, and the "Output Examples" section that restates the template add padding. Not score 3 because of this redundant boilerplate; not score 1 because the core template/Mermaid content is useful, not concept-explanation filler.

2 / 3

Actionability

Provides one genuinely executable artifact (the `C4Context` Mermaid block) and a structured output template, but the bulk is `[placeholder]` text and the Instructions give vague direction ("Apply relevant best practices and validate outcomes"). Not score 3 because key guidance is incomplete/pseudo-specified; not score 1 because the Mermaid code and labeled template fields are concrete.

2 / 3

Workflow Clarity

There is no sequenced production workflow with validation checkpoints; "validate outcomes" is mentioned abstractly without any concrete verification step. Not score 3 (no explicit checkpoints/feedback loop), not score 1 (the single documentation task and template provide an implicit structure, and no destructive/batch operation requires a hard validation gate).

2 / 3

Progressive Disclosure

Single self-contained file with well-organized sections (Use when, Instructions, System Overview, Personas, Features, Journeys, External Systems, Diagram, Template, Key Distinctions) and no multi-level reference chains; the in-template `./c4-container.md` links describe the generated output, not nested bundle references. Per the simple-skill note, well-organized sections without external references warrant a 3.

3 / 3

Total

9

/

12

Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states multiple capabilities and includes an explicit "Use when" trigger with a well-scoped niche. The only weakness is trigger-term phrasing that leans on repetitive C4 jargon rather than the natural terms a user would actually say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation" — matching the score-3 anchor of several specific actions rather than the single-action score-2 anchor.

3 / 3

Completeness

Clearly answers both what (creates diagrams, documents personas/journeys/features/dependencies, synthesizes architecture) and when ("Use when creating the highest-level C4 system context documentation"), in third-person voice with an explicit trigger — matching the score-3 anchor.

3 / 3

Trigger Term Quality

Includes relevant C4-domain terms ("C4 Context-level", "system context diagrams", "C4 system context documentation") but the trigger phrasing is jargon-heavy and repetitive ("highest-level", "context-level architecture"), missing common natural variations a user would say. Not score 3 because coverage of natural terms is uneven; not score 1 because the core C4/context keywords are present.

2 / 3

Distinctiveness Conflict Risk

The "highest-level C4 system context" niche is clearly scoped and distinct from sibling container/component/code levels (the body's Key Distinctions reinforce this), making wrong-skill triggering unlikely. Not score 2 because it is not merely "somewhat specific" — the level qualifier gives it a clear, non-overlapping niche.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
rmyndharis/antigravity-skills
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.