c4-architecture-c4-architecture

Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.

1.60x

Quality

58%

Does it follow best practices?

Impact

98%

1.60x

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/skills/c4-architecture-c4-architecture/SKILL.md

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

Quality

Content

63%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 highly actionable, well-sequenced guidance for coordinating the C4 subagents across four phases, with a useful success checklist. It is weakened by generic boilerplate sections, inlined prompt templates that belong in reference files, and a broken reference to a non-existent playbook.

Suggestions

Remove the generic 'Use this skill when' / 'Do not use this skill when' / 'Instructions' boilerplate and the 'Extended thinking' meta block; they restate the description without adding skill-specific value.

Move the large per-phase subagent prompt templates into reference files (e.g. references/code-prompt.md) and link to them from the body, fixing the dangling 'resources/implementation-playbook.md' reference.

Add explicit validation feedback loops between phases (e.g. verify every c4-code-*.md exists and contains required sections before proceeding to component synthesis) to strengthen the batch-operation workflow.

Dimension	Reasoning	Score
Conciseness	The core phase content is substantive and useful, but generic boilerplate sections ('Use this skill when', 'Do not use this skill when', 'Instructions') and the meta 'Extended thinking' block add unnecessary tokens that could be trimmed.	3 / 5
Actionability	Provides concrete, copy-paste-ready Task tool prompts with explicit subagent types, output filenames, directory conventions, and section structures; minor gaps remain from placeholders like [directory_path] that require filling.	4 / 5
Workflow Clarity	A clear four-phase bottom-up sequence with a Success Criteria checklist providing verification; however, explicit validate->fix->retry feedback loops for the batch directory processing are not spelled out.	4 / 5
Progressive Disclosure	The single 385-line SKILL.md inlines large prompt templates that could live in separate files, and its one external reference points to 'resources/implementation-playbook.md' which is not a present bundle file; structure exists but navigation is weak.	3 / 5
	Total	14 / 20 Passed

Description

53%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 third-person and clearly states what the skill does, but it omits any explicit 'when to use' trigger guidance and offers only a single concrete action. Adding a 'Use when...' clause with natural trigger phrases would substantially improve it.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks for C4 architecture diagrams, system context/container/component documentation, or a bottom-up architectural analysis of a codebase.'

Broaden trigger terms with natural synonyms users say, such as 'architecture diagrams', 'system context diagram', 'container diagram', and 'component diagram'.

List one or two more concrete actions (e.g. 'generate Mermaid C4 diagrams' or 'produce OpenAPI specs for container APIs') to lift specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	Names the domain ('C4 architecture documentation') and a concrete action ('Generate comprehensive C4 architecture documentation') with a method ('bottom-up analysis approach'), but covers only one main action rather than a comprehensive set.	3 / 5
Completeness	Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes relevant keywords like 'C4 architecture documentation' and 'repository/codebase' that a user might say, but misses common synonyms/variations such as 'architecture diagrams', 'system context', or 'container diagram'.	3 / 5
Distinctiveness Conflict Risk	'C4 architecture documentation' is a fairly distinct niche with specific triggers; minor overlap risk exists with general architecture/documentation skills but it is mostly distinguishable.	4 / 5
	Total	13 / 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/skills/c4-architecture-c4-architecture/SKILL.md
Commit: 57c135b

Reviewed: 2 days 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.