c4-code
tessl i github:sickn33/antigravity-awesome-skills --skill c4-codeExpert 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Implementation
22%This skill is a documentation template rather than actionable guidance. It explains what C4 Code-level documentation should contain and shows extensive Mermaid diagram examples, but fails to provide concrete steps for how Claude should analyze code directories, extract information, or produce the documentation. The content assumes Claude needs to learn Mermaid syntax and C4 concepts it already knows.
Suggestions
Replace the generic 4-bullet instruction list with a concrete workflow: 1) List files in directory, 2) Parse each file for functions/classes, 3) Extract signatures and dependencies, 4) Generate documentation following template, 5) Validate completeness
Remove or move to a reference file the extensive Mermaid diagram examples and 'Choosing the Right Diagram' table - Claude knows Mermaid syntax
Add specific commands or code for extracting function signatures, dependencies, and code structure (e.g., using AST parsing, grep patterns, or language-specific tools)
Include a concrete example showing input (a real code snippet) and expected output (the resulting C4 documentation) rather than just template placeholders
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely verbose with extensive template placeholders, multiple diagram options with full examples, and explanatory tables. Much of this (Mermaid syntax, diagram types, C4 model concepts) is knowledge Claude already possesses and doesn't need to be taught. | 1 / 3 |
Actionability | Provides template structure and diagram examples, but the actual instructions are vague ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices'). The code examples are templates with placeholders rather than executable guidance for analyzing real code. | 2 / 3 |
Workflow Clarity | No clear workflow for how to actually analyze a codebase and produce C4 documentation. The instructions section has only four bullet points of generic advice. Missing: how to traverse directories, what to extract, validation steps, iteration process. | 1 / 3 |
Progressive Disclosure | References 'resources/implementation-playbook.md' for detailed examples, which is appropriate. However, the main content includes extensive inline diagram examples and tables that could be moved to reference files, making the skill unnecessarily long. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
85%This is a well-structured skill description that clearly defines its purpose within the C4 documentation framework. It excels at specificity and completeness with an explicit 'Use when' clause. The main weakness is trigger term coverage - it relies heavily on users knowing C4 terminology rather than including natural language variations they might use.
Suggestions
Add natural language trigger terms users might say, such as 'document my code', 'code documentation', 'API docs', or 'module documentation'
Include common file/directory references like 'source files', 'codebase', or specific language mentions if applicable
| 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 answers both what ('Analyzes code directories to create comprehensive 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 some relevant terms like 'C4', 'code-level documentation', 'function signatures', 'dependencies', but misses common variations users might say like 'document my code', 'code docs', 'API documentation', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | The 'C4 code-level' specification creates a clear niche distinct from general documentation skills. The focus on 'lowest C4 level' and specific outputs (function signatures, arguments, dependencies) makes it unlikely to conflict with other documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Reviewed
Table of Contents
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.