c4-code

Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.

1.84x

Quality

37%

Does it follow best practices?

Impact

94%

1.84x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/c4-code/SKILL.md

The canonical home for this skill is c4-code in sickn33/antigravity-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 an empty template with placeholder values rather than actionable guidance. It provides extensive Mermaid diagram examples for different paradigms but lacks any concrete workflow for how to actually analyze code directories, extract function signatures, or build C4 code-level documentation. The content is verbose with explanatory material Claude doesn't need while missing the critical 'how to do it' instructions.

Suggestions

Replace placeholder brackets with a concrete, step-by-step workflow: e.g., 1) List files in directory, 2) Read each file and extract function/class signatures, 3) Map dependencies between elements, 4) Generate documentation following the template, 5) Validate completeness.

Move the extensive Mermaid diagram examples and paradigm comparison table to a separate reference file (e.g., resources/diagram-templates.md) and keep only a brief summary with links in the main skill.

Add concrete examples of actual code analysis - show a real code snippet and the expected C4 documentation output, rather than only template placeholders.

Remove the generic instructions ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') and replace with specific, actionable steps for code analysis including validation checkpoints.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose and mostly consists of template placeholders ([Directory Name], [What this function does], etc.) rather than actionable content. The extensive Mermaid diagram examples for every paradigm (OOP, FP, procedural, mixed) bloat the file significantly. The 'choosing the right diagram' table and lengthy explanations of when to use each diagram type explain concepts Claude already understands.	1 / 3
Actionability	The content is entirely template-based with placeholder brackets throughout. There are no concrete, executable steps for how to actually analyze a codebase - no commands to run, no real code examples, no specific tools or approaches. The Mermaid diagrams are illustrative templates, not actionable instructions for performing code analysis.	1 / 3
Workflow Clarity	There is no clear workflow for how to analyze code and produce C4 documentation. The instructions section has only four vague bullet points ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices'). There's no sequenced process for reading code, extracting signatures, building dependency graphs, or validating the output documentation.	1 / 3
Progressive Disclosure	There is a reference to 'resources/implementation-playbook.md' for detailed examples, and the document has clear section headers. However, the massive inline Mermaid diagram examples and the comparison table should be in a separate reference file rather than in the main skill body, making the overview far too long.	2 / 3
	Total	5 / 12 Passed

Description

67%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 is strong in specificity and distinctiveness, clearly identifying the C4 code-level documentation niche with concrete deliverables. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. The trigger terms could also be expanded to cover more natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for C4 diagrams, code-level architecture documentation, or wants to map out code structure and dependencies.'

Include additional natural trigger terms users might say, such as 'architecture documentation', 'code map', 'component dependencies', 'codebase structure', or 'software architecture'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Analyzes code directories', 'create comprehensive C4 code-level documentation', 'function signatures, arguments, dependencies, and code structure'. These are concrete, specific capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' (analyzes code directories to create C4 code-level documentation with specific outputs), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes relevant terms like 'C4', 'code-level documentation', 'function signatures', 'dependencies', 'code structure', but misses common user variations like 'architecture diagram', 'component diagram', 'code map', or file extensions. Users might not always say 'C4' specifically.	2 / 3
Distinctiveness Conflict Risk	The 'C4 code-level documentation' niche is very specific and distinct. It's unlikely to conflict with general code documentation or other architecture skills because it explicitly targets the C4 model's code level with specific deliverables like function signatures and dependencies.	3 / 3
	Total	10 / 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: skills/c4-code/SKILL.md
Commit: 0159794

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