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.

73

1.34x
Quality

61%

Does it follow best practices?

Impact

97%

1.34x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/c4-context/SKILL.md

The canonical home for this skill is c4-context in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 body delivers a practical C4 context template plus a concrete Mermaid example, but it is undermined by vague instruction prose, a dangling reference to a missing file, and a markdown formatting error.

Suggestions

Fix or remove the broken reference to `resources/implementation-playbook.md` — either create the file under `references/` and update the path, or drop the pointer.

Remove the stray ``` fence after the Related Documentation list (line 87) and tighten the generic "Instructions" bullets into concrete steps with validation checkpoints.

Trim the redundant "Output Examples" section since the template already enumerates the same deliverables, improving token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient with a useful template scaffold and Mermaid example, but padded by generic "Instructions" filler ("Apply relevant best practices and validate outcomes") and an "Output Examples" list that duplicates what the template already specifies.

3 / 5

Actionability

Provides a copy-paste-ready Mermaid C4Context example and a concrete template structure with labeled fields; the only gap is the vague surrounding instruction prose.

4 / 5

Workflow Clarity

A rough sequence exists (clarify goals → apply best practices → provide steps and verification) but the steps are generic and lack explicit validation checkpoints, so checkpoints are only implicit.

3 / 5

Progressive Disclosure

Sections are reasonably organized, but the one external reference ("open `resources/implementation-playbook.md`") points to a non-existent path with no bundle directory present, and a stray ``` fence on line 87 breaks the markdown structure.

3 / 5

Total

13

/

20

Passed

Description

66%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.

A solid, domain-specific description that names concrete documentation actions and is clearly distinguishable, but it lacks an explicit "Use when..." trigger clause so the "when" side of completeness is only weakly implied.

Suggestions

Append an explicit trigger clause, e.g. "Use when creating C4 system context documentation, modeling personas and user journeys, or mapping external system dependencies."

Add a couple of natural synonyms/file cues (e.g. "C4 context diagram", ".c4", "architecture context") to broaden trigger-term coverage.

Tighten actions toward more concrete outputs (e.g. "generates Mermaid C4Context diagrams") to lift specificity toward 5.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies" — but the actions are high-level documentation verbs rather than sharply concrete operations, leaving minor coverage gaps.

4 / 5

Completeness

It clearly answers the "what" (creates context diagrams and documents personas/journeys/features/dependencies) but provides no explicit "when"/"Use when..." trigger clause, capping completeness at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

Contains natural domain keywords users would say ("C4 Context-level", "system context diagrams", "personas", "user journeys") with good coverage, but misses common synonyms and any file-extension cues.

4 / 5

Distinctiveness Conflict Risk

"C4 Context-level documentation specialist" carves a clear niche distinct from sibling C4 skills, with only minor overlap risk against the closely related Container/Component/Code variants.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.