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

51%

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

43%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 skill provides a usable structured template and a solid Mermaid example, but its workflow is vague and checkpoint-free, instructions are generic boilerplate, and the one external reference points to a non-existent file.

Suggestions

Replace the vague Instructions bullets with a concrete, sequenced workflow with validation checkpoints (synthesize c4-code-*.md files → propose boundaries → document interfaces → validate Mermaid renders → assemble master index).

Fix or remove the dangling `resources/implementation-playbook.md` reference — neither a `resources/` nor `references/` bundle directory exists — and place any detailed examples under a real `references/` directory.

Replace generic boilerplate ('Apply relevant best practices and validate outcomes') with C4-specific actionable guidance, e.g., explicit rules for grouping code files into components and naming interfaces.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and does not over-explain C4 concepts, but generic boilerplate such as 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices and validate outcomes' adds little and could be tightened.	3 / 5
Actionability	A concrete, copy-pasteable Mermaid C4Component block is provided, but most of the guidance is bracketed placeholders ([Component name], [Description]) and vague instruction bullets rather than fully executable specifics.	3 / 5
Workflow Clarity	Only a rough, poorly-defined sequence is implied by the generic Instructions bullets ('Clarify goals' → 'Apply best practices' → 'Provide actionable steps'); there are no explicit validation checkpoints, and the sole detailed-examples reference is a dangling path.	2 / 5
Progressive Disclosure	The body is reasonably sectioned with headers and includes a reference to implementation-playbook.md for detail, but that referenced path (resources/) does not exist and substantial template content is inlined rather than split out.	3 / 5
	Total	11 / 20 Passed

Description

58%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, specific 'what' and is reasonably distinct within the C4 family, but it lacks any explicit 'when to use' trigger guidance and relies on a single narrow keyword phrasing.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when creating C4 component diagrams or synthesizing code-level documentation into component architecture').

Include natural trigger synonyms users would actually say, such as 'component diagram', 'component architecture', or 'component boundaries', to broaden keyword coverage.

Optionally mention the concrete outputs (component diagrams, master component index) to round out capability coverage toward a 5 on specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships' — but coverage is not comprehensive (no mention of diagrams, outputs, or the master index), stopping short of a 5.	4 / 5
Completeness	It clearly answers the 'what' (synthesize code-level docs into component architecture, defining boundaries/interfaces/relationships) but provides no 'Use when...' trigger clause, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	The core natural phrase 'C4 Component-level documentation' is present and is what a user would say, but it offers only that single narrow phrasing with no common variations or synonyms like 'component diagram' or 'architecture documentation'.	3 / 5
Distinctiveness Conflict Risk	The repeated 'C4 Component-level' framing carves a mostly-distinct niche with only minor overlap risk against sibling C4 skills (code/container/context), though those siblings are closely related.	4 / 5
	Total	14 / 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-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.