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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

47%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 content is a well-structured documentation template with useful Mermaid guidance, but it is padded with lengthy diagram examples, leans on placeholders and generic instructions, and lacks a concrete sequenced workflow with validation checkpoints.

Suggestions

Replace the generic 'Instructions' bullets with a numbered, sequenced documentation workflow (e.g., 1. survey directory, 2. extract signatures, 3. map dependencies, 4. draft diagram, 5. validate against source) with explicit validation checkpoints.

Move the three full Mermaid example blocks into a separate references file and keep only a short 'choosing a diagram type' summary plus one compact example inline to reduce token padding.

Replace placeholder-heavy guidance with concrete, fillable instructions (e.g., specify how to locate function signatures per language, or point to scripts/commands for extracting them) so the skill yields executable rather than skeleton output.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but carries substantial illustrative padding — three full Mermaid diagram examples plus a decision table — that inflates token usage beyond what a lean overview needs, fitting the score-3 anchor.	3 / 5
Actionability	Provides a concrete documentation template (signature format, dependency lists, Mermaid syntax) but relies heavily on placeholders like '[file path:line number]' and generic directives ('Clarify goals, constraints, and required inputs'), yielding incomplete/skeleton guidance rather than fully executable instructions.	3 / 5
Workflow Clarity	The 'Instructions' are generic ('Apply relevant best practices and validate outcomes') with no sequenced steps or concrete validation checkpoints; only a rough implied structure (overview → code elements → dependencies → relationships) is present, matching the score-2 anchor.	2 / 5
Progressive Disclosure	Well-organized with clear section headers and a single one-level external reference (c4model.com); structure is good though the three full Mermaid examples could be moved to a reference file, fitting the score-4 anchor.	4 / 5
	Total	12 / 20 Passed

Description

88%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 is strong: concrete, third-person, and explicit about both what the skill does and when to use it, with good trigger terms. The main weakness is minor overlap risk with related C4-level skills and a few missing natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (analyzes code directories, creates C4 code-level documentation capturing function signatures, arguments, dependencies, and code structure), giving comprehensive domain-specific coverage matching the score-5 anchor.	5 / 5
Completeness	Explicitly states both the 'what' (analyze code directories to produce C4 code-level docs with signatures/args/deps/structure) and the 'when' ('Use when documenting code at the lowest C4 level for individual directories and code modules'), matching the score-5 anchor.	5 / 5
Trigger Term Quality	Includes natural terms like 'C4 code level', 'documenting code', 'code modules', and 'function signatures', but misses common synonyms/variations such as 'code documentation', 'source code', or file extensions, fitting the score-4 anchor.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche (lowest C4 level, individual directories/modules), but overlaps somewhat with sibling C4 skills (Context, Container, Component) referenced in the body, placing it at the score-4 anchor rather than 5.	4 / 5
	Total	18 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/c4-code/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.