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. Use when documenting code at the lowest C4 level for individual directories and code modules.

Quality

46%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/c4-code/SKILL.md

Quality

Content

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

This skill is an unfilled template with placeholder values throughout. It provides no actionable guidance for creating C4 code-level documentation—no concrete examples of what the output should look like, no specific analysis steps, and no executable code or commands. The only partial strength is the sub-skill file structure, but without actual content in the main file or verified bundle files, it serves no practical purpose.

Suggestions

Replace all placeholder brackets with actual content or, if this is meant to be a reusable template, provide at least one fully worked example showing a completed C4 code-level document for a real directory.

Add concrete, actionable steps for analyzing a code directory—e.g., specific commands to list functions, extract dependencies, or generate diagrams—rather than generic instructions like 'Apply relevant best practices.'

Include an example output showing what a completed C4 code-level document looks like (function signatures, dependency graphs, class diagrams) so Claude knows the expected deliverable format.

Consolidate the 10 overlapping sub-skills (e.g., 'Functions/Methods' and 'Functional/Procedural Code' overlap significantly) and provide brief inline summaries of what each sub-skill covers before linking out.

Dimension	Reasoning	Score
Conciseness	The content is a hollow template filled with placeholders like '[Directory Name]', '[Short description]', etc. It provides no actual information and wastes tokens on generic boilerplate instructions ('Clarify goals, constraints, and required inputs') that Claude already knows how to do.	1 / 3
Actionability	There are no concrete steps, executable code, specific commands, or real examples. Every section is either a placeholder or vague directive like 'Apply relevant best practices and validate outcomes.' Claude cannot act on any of this content.	1 / 3
Workflow Clarity	There is no defined workflow, no sequenced steps, and no validation checkpoints. The 'Instructions' section lists four generic bullet points that provide no meaningful process guidance for creating C4 code-level documentation.	1 / 3
Progressive Disclosure	The skill does reference 10 sub-skill files and a resources file, which shows an attempt at progressive disclosure with one-level-deep references. However, no bundle files were provided to verify these exist, the sub-skill names are redundant/overlapping (e.g., 'Functions/Methods' vs 'Functional/Procedural Code'), and the main file provides zero overview content to orient the reader before navigating to sub-skills.	2 / 3
	Total	5 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-structured skill description that clearly identifies its niche (C4 code-level documentation), lists specific capabilities, and includes an explicit 'Use when' clause. Its main weakness is that trigger term coverage could be broader to capture users who might describe the same need using different terminology (e.g., 'code docs', 'API docs', 'class-level architecture').

Suggestions

Add more natural trigger term variations that users might say, such as 'code docs', 'API documentation', 'class diagrams', 'module documentation', or 'Level 4 diagram' to improve discoverability.

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 both 'what' (analyzes code directories to create C4 code-level documentation including function signatures, arguments, dependencies, and code structure) and 'when' (Use when documenting code at the lowest C4 level for individual directories and code modules).	3 / 3
Trigger Term Quality	Includes relevant terms like 'C4', 'code-level documentation', 'function signatures', 'dependencies', 'code structure', and 'code modules'. However, it misses common user variations like 'class diagram', 'code architecture', 'code docs', 'API documentation', or file-type triggers. The term 'C4' is somewhat niche and users may not always use it.	2 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche: C4 code-level (Level 4) documentation specifically for individual directories and modules. This is distinct from general code documentation, higher-level C4 diagrams (context, container, component), and other documentation skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: Dokhacgiakhoa/antigravity-ide
Commit: c4a059b

Reviewed: 5 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.