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.

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill c4-code

What are skills?

1.84x

Review — 28%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Evaluation — 94%

↑ 1.84x

Agent success when using this skill

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

50%

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 excels at specificity and carves out a distinct niche with C4 code-level documentation, but critically lacks any 'Use when...' guidance that would help Claude know when to select this skill. The trigger terms are adequate but could include more natural user phrasings like 'document my code' or 'architecture documentation'.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks for C4 diagrams, code documentation, architecture documentation, or wants to document code structure and dependencies'

Include natural user phrasings as trigger terms: 'document my code', 'code architecture', 'generate documentation', 'code docs'

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, actionable capabilities.	3 / 3
Completeness	Clearly describes WHAT it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for WHEN Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all.	1 / 3
Trigger Term Quality	Includes relevant terms like 'C4', 'code-level documentation', 'function signatures', 'dependencies', but misses common variations users might say like 'architecture diagram', 'code docs', 'document my code', or 'code structure diagram'.	2 / 3
Distinctiveness Conflict Risk	The 'C4 Code-level' specification creates a clear niche distinct from general documentation tools. The focus on C4 model specifically and code-level (vs container/component level) makes it unlikely to conflict with other documentation skills.	3 / 3
	Total	9 / 12 Passed

Implementation

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 text rather than actionable guidance. It explains what C4 Code-level documentation should contain but provides no concrete examples, no actual analysis workflow, and no executable commands. The extensive Mermaid diagram tutorials consume significant tokens while teaching concepts Claude already knows.

Suggestions

Replace placeholder text with one concrete, complete example showing actual code analysis output (e.g., document a real function with signature, description, and dependencies)

Add a clear step-by-step workflow: 1) Identify entry points, 2) Extract function signatures, 3) Map dependencies, 4) Generate diagram, with validation at each step

Move the extensive Mermaid diagram tutorial to a separate reference file and keep only a brief pointer in the main skill

Remove the generic instructions section ('Clarify goals, constraints...') and replace with specific commands or analysis patterns Claude should follow

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose with extensive template boilerplate, multiple diagram examples, and explanatory tables that Claude already understands. The content explains basic concepts like 'what this function does' placeholders and includes lengthy Mermaid diagram tutorials that add significant token overhead without providing actionable guidance.	1 / 3
Actionability	The skill provides only template placeholders like '[Descriptive name for this code directory]' and '[What this function does]' without any concrete, executable examples. There are no actual code analysis commands, no real function signatures to demonstrate the format, and no copy-paste ready content.	1 / 3
Workflow Clarity	The instructions section contains only vague directives like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices' without any clear sequence of steps for analyzing code or creating documentation. No validation checkpoints or feedback loops are provided for the documentation process.	1 / 3
Progressive Disclosure	The skill references 'resources/implementation-playbook.md' for detailed examples, which is appropriate progressive disclosure. However, the main content is a monolithic wall of template text with extensive inline Mermaid diagram examples that should be in a separate reference file.	2 / 3
	Total	5 / 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

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.