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.
39
37%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/c4-code/SKILL.mdQuality
Discovery
67%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 does well at specifying concrete capabilities and occupying a clear niche (C4 code-level documentation), making it distinctive. However, it lacks an explicit 'Use when...' clause which hurts completeness, and could benefit from more natural trigger terms that users would actually say when requesting this type of documentation.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for C4 diagrams, code-level architecture documentation, or wants to document code structure using the C4 model.'
Include additional natural trigger terms like 'C4 model', 'C4 diagram', 'architecture documentation', 'code docs', or 'document codebase' to improve keyword coverage.
| 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 'what does this do' (analyzes code directories to create C4 code-level documentation with specific outputs), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'C4', 'code-level documentation', 'function signatures', 'dependencies', 'code structure', but misses common user variations like 'C4 model', 'C4 diagram', 'architecture documentation', or 'code docs'. Users might say 'C4 diagram' or 'document my code' which aren't well covered. | 2 / 3 |
Distinctiveness Conflict Risk | The 'C4 code-level documentation' niche is very specific and distinct. It's unlikely to conflict with general documentation skills or other architecture skills because it targets a specific level (code-level) of a specific framework (C4). | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
7%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 unfilled template with placeholder values throughout, providing no concrete or actionable guidance for Claude. It spends significant token budget on Mermaid diagram examples for multiple paradigms and a comparison table, all of which represent general C4 knowledge Claude likely already has. The skill lacks any real workflow for analyzing code directories and producing documentation.
Suggestions
Replace placeholder brackets with concrete, executable instructions describing the actual steps to analyze a code directory (e.g., 'List all files with `find`, parse function signatures, identify imports for dependencies').
Add a clear numbered workflow with validation checkpoints, such as: 1) Scan directory structure, 2) Extract function signatures, 3) Map dependencies, 4) Verify completeness against file listing, 5) Generate output.
Drastically reduce the Mermaid diagram section—provide one concise example and a brief note on choosing diagram types rather than full examples for every paradigm.
Remove generic instructions like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices' which add no value for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is a template full of placeholder brackets like [Directory Name], [What this function does], etc. It's extremely verbose with extensive Mermaid diagram examples for every paradigm (OOP, FP, procedural, mixed), a comparison table, and lengthy example interactions. Much of this is general C4 knowledge Claude already possesses, and the template placeholders add no actionable value. | 1 / 3 |
Actionability | The content provides no concrete, executable guidance. It's entirely a template with placeholder values and generic instructions like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices.' The Mermaid diagrams are illustrative templates rather than executable steps for actually analyzing code directories. | 1 / 3 |
Workflow Clarity | There is no clear multi-step workflow for how to actually analyze a code directory and produce C4 code-level documentation. The instructions section has only four vague bullet points with no sequencing, no validation checkpoints, and no feedback loops for verifying the accuracy of generated documentation. | 1 / 3 |
Progressive Disclosure | There is a reference to `resources/implementation-playbook.md` for detailed examples, which shows some attempt at progressive disclosure. However, no bundle files are provided to verify this reference, and the main document itself is a monolithic wall of template content and diagram examples that could be split into separate reference files. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
90%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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
8854d4e
- 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.