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.

Quality

58%

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

57%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, well-structured C4 code-level documentation template with executable mermaid examples, but it is padded with generic instructional filler, lacks concrete validation checkpoints, and references a non-existent playbook file.

Suggestions

Replace the generic Instructions bullets with concrete analysis steps (e.g. enumerate functions via grep/AST, extract signatures, resolve imports) instead of 'Apply relevant best practices and validate outcomes'.

Create the referenced resources/implementation-playbook.md or remove the dangling reference so progressive disclosure is not broken.

Add an explicit validation checkpoint in the workflow (e.g. 'Verify every listed function signature against the source file before emitting the diagram') to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete mermaid examples, but the Instructions section is generic filler ('Apply relevant best practices and validate outcomes') and three full diagram examples add padding, matching the score-3 anchor with some unnecessary content.	3 / 5
Actionability	Provides copy-paste-ready mermaid diagrams and a concrete fill-in template for functions, classes, and dependencies; minor gaps remain in the actual code-analysis steps, matching the score-4 anchor.	4 / 5
Workflow Clarity	A rough sequence exists ('Clarify goals... Apply best practices... validate outcomes') and the Limitations note a stop-and-ask checkpoint, but validation is mentioned only abstractly with no concrete checkpoints, matching the score-3 anchor.	3 / 5
Progressive Disclosure	The body is well-sectioned into clear headers, but the sole external reference ('resources/implementation-playbook.md') points to a file that does not exist in any bundle directory, leaving structure present but the reference broken, matching the score-3 anchor.	3 / 5
	Total	13 / 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 clearly states what the skill does and names concrete documentation elements, but it omits any 'Use when...' trigger guidance and lacks synonym/extension coverage, capping completeness and trigger-term quality at the midpoint.

Suggestions

Append an explicit trigger clause, e.g. 'Use when creating C4 code-level documentation for a code directory, or when the user asks to document function signatures, dependencies, or code structure.'

Add natural synonyms and concrete triggers users would say ('document the code in', 'C4 code diagram', 'function-level docs') to broaden keyword coverage.

Briefly distinguish from sibling C4 skills in the description itself (e.g. 'code-level detail, not component or container diagrams') to reduce overlap risk.

Dimension	Reasoning	Score
Specificity	Lists several concrete elements ('function signatures, arguments, dependencies, and code structure') under a create-documentation action, comparable to the score-4 anchor with minor coverage gaps; not a 5 because these are sub-elements of one action rather than multiple distinct actions.	4 / 5
Completeness	The 'what' is clear ('Analyzes code directories to create comprehensive C4 code-level documentation...') but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'C4 code-level documentation' and 'code directories' are relevant terms a user might say, but common variations or synonyms are missing, matching the score-3 anchor rather than the comprehensive coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	'C4 Code-level documentation' is a clear niche with minimal conflict risk, though minor overlap exists with sibling C4 skills (component/container/context), matching the score-4 anchor rather than the fully-distinct 5.	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: sickn33/antigravity-awesome-skills
Path: skills/c4-code/SKILL.md
Commit: 1f67c44

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.