c4-component

Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships.

3.12x

Quality

58%

Does it follow best practices?

Impact

100%

3.12x

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-component/SKILL.md

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

Quality

Content

50%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 is a well-structured C4 component-level documentation template with a concrete Mermaid example and useful distinctions, but it leans heavily on placeholders, vague boilerplate instructions, lacks validation checkpoints, and references a bundle file that does not exist.

Suggestions

Replace vague Instructions ("Apply relevant best practices and validate outcomes") with a concrete, sequenced workflow for synthesizing c4-code files into components, including an explicit validation step (e.g., verify every code element is mapped to a component and all interfaces are documented).

Fix or remove the dangling reference to resources/implementation-playbook.md — either create the file under a real bundle directory (references/) or drop the pointer.

Move the Master Component Index Template and full Mermaid examples into separate reference files so SKILL.md stays a lean overview with clearly signaled, one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining C4 concepts Claude already knows, but includes redundancy (the Key Principles repeat the Mermaid diagram, and "Do not use this skill when" mirrors "Use this skill when") plus placeholder scaffolding that could be tightened.	3 / 5
Actionability	The Mermaid C4Component example and Key Distinctions are concrete and usable, but the core Instructions are vague boilerplate ("Apply relevant best practices and validate outcomes") and most of the template is uninstantiated placeholders, with a reference to a non-existent resources/implementation-playbook.md.	3 / 5
Workflow Clarity	A rough sequence is implied via the template structure and generic instructions, but there are no concrete validation checkpoints for this batch synthesis operation, so workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	Section organization is reasonable, but there are no actual bundle files and the single reference to resources/implementation-playbook.md is broken (the path does not exist), while content that could live in separate files (e.g., the Master Component Index template) is inlined.	3 / 5
	Total	12 / 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 clearly states what the skill does with several concrete C4-component actions and is reasonably distinctive within the C4 family, but it omits any explicit "Use when..." trigger guidance, capping completeness at 3.

Suggestions

Add an explicit "Use when..." clause naming concrete triggers (e.g., "Use when creating or updating C4 component-level documentation, synthesizing c4-code files into components, or drawing C4Component diagrams").

Include natural user phrasings and synonyms like "component diagram" and "C4 model" to broaden trigger coverage.

Clarify how it differs from sibling skills directly in the description to reduce conflict risk with C4-Code/Container/Context.

Dimension	Reasoning	Score
Specificity	"Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships" lists several concrete actions (synthesize, define boundaries, interfaces, relationships), though coverage is not fully comprehensive (e.g., no mention of diagrams or validation).	4 / 5
Completeness	The description gives a clear "what" but includes no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Terms like "C4 Component-level documentation", "C4 Code-level documentation", and "Component-level architecture" are natural for C4-model users, but common variations such as "component diagram", "C4 model", or file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	"C4 Component-level documentation specialist" carves a mostly distinct niche, but the body itself notes overlap with sibling C4-Code, C4-Container, and C4-Context skills, indicating minor conflict risk with closely related 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/c4-component/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.