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

20%

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

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

Quality

Content

7%Scale 1-3

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

This skill is essentially a blank template with placeholders rather than actionable guidance. It fails to provide concrete steps for synthesizing C4 code-level documentation into component-level architecture, instead offering generic section headers with bracket placeholders. The Mermaid diagram example is the only semi-concrete element, but even it uses placeholder names.

Suggestions

Replace placeholder brackets with a concrete, worked example showing how to synthesize actual code-level files into a component document, demonstrating the full process end-to-end.

Add a clear step-by-step workflow: e.g., 1) Read all c4-code-*.md files, 2) Identify logical groupings by responsibility, 3) Define component boundaries, 4) Document interfaces, 5) Validate completeness against a checklist.

Remove generic instructions ('Clarify goals, constraints, and required inputs') and C4 concept explanations Claude already knows; replace with specific decision criteria for component boundary identification.

Move the template sections (Overview, Interfaces, Dependencies) to a separate template file and keep the SKILL.md focused on the synthesis process and decision-making guidance.

Dimension	Reasoning	Score
Conciseness	The skill is a template full of placeholders ([Component Name], [Description], etc.) rather than actionable content. It includes unnecessary boilerplate like 'Use this skill when' / 'Do not use this skill when' sections that are tautological, and explains C4 concepts Claude already knows. The 'Key Principles' section restates basic C4 model knowledge.	1 / 3
Actionability	Almost entirely placeholder-driven with no concrete, executable guidance. There are no real code examples, no specific commands, and no actual steps to follow—just template brackets like '[Component name]', '[Description]', '[Feature 1]'. The instructions section is generic ('Clarify goals, constraints, and required inputs') rather than specific to the task.	1 / 3
Workflow Clarity	There is no clear multi-step workflow for synthesizing code-level documentation into component-level architecture. The 'Instructions' section has four vague bullet points with no sequencing, no validation checkpoints, and no feedback loops. The 'Example Interactions' section lists prompts but not how to execute them.	1 / 3
Progressive Disclosure	There is a reference to 'resources/implementation-playbook.md' and the structure separates concerns into sections (Overview, Interfaces, Dependencies, Diagrams). However, the content that should be in the main skill (actual instructions) is missing, and the template content that could be in a separate reference file is inline.	2 / 3
	Total	5 / 12 Passed

Description

32%Scale 1-3

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 identifies a clear domain niche (C4 Component-level documentation) and mentions the synthesis from Code-level to Component-level, which provides some specificity. However, it lacks a 'Use when...' clause entirely, uses somewhat jargon-heavy language without common user trigger terms, and could easily be confused with other C4-level documentation skills without clearer differentiation.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create or update C4 Component diagrams, consolidate code-level details into component architecture, or define component boundaries and interfaces.'

Include natural trigger term variations users might say, such as 'C4 model', 'C4 diagram', 'component diagram', 'architecture docs', or 'system components'.

Differentiate from other C4-level skills by explicitly stating what levels this skill handles versus what it does not (e.g., 'Does not handle Context or Container level diagrams').

Dimension	Reasoning	Score
Specificity	Names the domain (C4 Component-level documentation) and some actions ('synthesizes', 'defining component boundaries, interfaces, and relationships'), but doesn't list multiple concrete discrete actions like generating diagrams, producing specific output formats, or validating architecture.	2 / 3
Completeness	Describes what it does (synthesizes C4 Code-level into Component-level architecture) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'when' is entirely absent, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'C4', 'Component-level', 'Code-level', 'architecture', 'component boundaries', and 'interfaces', but misses common user variations like 'C4 model', 'C4 diagram', 'architecture documentation', 'component diagram', or 'system design'.	2 / 3
Distinctiveness Conflict Risk	The C4 Component-level focus is fairly specific, but it could overlap with other C4-related skills (e.g., C4 Context-level, C4 Container-level, or general architecture documentation skills) without explicit differentiation of when to choose this one over those.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/c4-component/SKILL.md
Commit: 7520423

Reviewed: ~16 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.