c4-context

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

1.34x

Quality

65%

Does it follow best practices?

Impact

97%

1.34x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

Quality

Content

65%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 is a well-structured, mostly efficient documentation template with a concrete Mermaid example, but its workflow is vaguely sequenced without real validation checkpoints and it carries a dangling reference to a missing playbook file.

Suggestions

Replace the generic 'Instructions' steps with a concrete, sequenced workflow with an explicit validation checkpoint (e.g., 'Draft diagram -> verify every persona and external system is represented -> confirm no technologies/protocols appear').

Fix or remove the broken 'resources/implementation-playbook.md' reference; if a playbook is intended, create it under 'references/' and link it with a clear 'See references/implementation-playbook.md for worked examples'.

Trim the overlap between 'Example Interactions' and 'Output Examples' and remove the stray code fence after 'Related Documentation' to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is a lean template with placeholders and a focused Mermaid example that mostly assumes Claude's competence; minor redundancy between 'Example Interactions' and 'Output Examples' and a stray code fence on the 'Related Documentation' line keep it just below the fully lean 5 anchor.	4 / 5
Actionability	It provides a concrete, fill-in documentation template plus a copy-pasteable Mermaid C4Context code block with real syntax, which is actionable guidance with only minor gaps from the bracketed placeholder abstractions.	4 / 5
Workflow Clarity	The 'Instructions' section gives only a vague three-step sequence ('Clarify goals... Apply relevant best practices and validate outcomes') with no concrete validation checkpoints or feedback loop, matching 'steps present but checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	The single file has reasonable section headers but no bundle files exist, and the body references 'resources/implementation-playbook.md' which is neither present nor in the expected 'references/' location, leaving a broken, poorly-signaled reference.	3 / 5
	Total	14 / 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.

The description conveys a clear, moderately specific capability set for C4 Context-level documentation with reasonable domain trigger terms, but it omits any explicit 'when to use' guidance and only weakly distinguishes itself from sibling C4 skills.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when creating a C4 System Context diagram or documenting personas, user journeys, and external system dependencies').

Sharpen the action verbs beyond generic 'documents' (e.g., 'maps personas to features', 'draws Mermaid C4Context diagrams') to lift specificity toward comprehensive coverage.

Add a distinguishing cue against sibling skills (e.g., 'high-level system scope, not container/component/code-level detail') to reduce conflict risk.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies'), but they remain somewhat generic ('documents personas') rather than crisply distinct, fitting 'several specific actions; minor gaps' better than the comprehensive 5 anchor.	4 / 5
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so per the rubric a missing explicit 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	Domain terms like 'C4 Context-level', 'system context diagrams', 'personas', and 'user journeys' are natural phrases a user working with the C4 model would say, giving good keyword coverage, though common synonyms/extensions are not exhaustive so it stops short of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The 'C4 Context-level' niche is mostly distinct, but the description does not sharply differentiate it from sibling C4 skills (Container, Component, Code), leaving minor overlap risk rather than the minimal-conflict 5 anchor.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/c4-context/SKILL.md
Commit: 57c135b

Reviewed: 22 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.