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.
49
37%
Does it follow best practices?
Impact
Pending
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 carving out a distinct niche around C4 code-level documentation. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. The trigger terms could also be expanded to include more natural user language variations.
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 more natural trigger term variations such as 'C4 model', 'architecture documentation', 'code diagram', 'component documentation', or 'software architecture'.
| 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 'architecture diagram', 'code diagram', 'C4 model', 'component diagram', or file types. Users might not naturally say 'C4 code-level documentation specialist'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'C4 code-level documentation' niche is very specific and distinct. It's unlikely to conflict with general code documentation skills or other architecture documentation skills due to the explicit C4 framework reference and code-level specificity. | 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 creating C4 code-level documentation. The extensive Mermaid diagram examples for every programming paradigm are verbose and represent knowledge Claude already has. The skill lacks any real workflow, validation steps, or executable instructions for analyzing code directories.
Suggestions
Replace placeholder template with concrete, executable instructions: define a clear step-by-step workflow for analyzing a code directory (e.g., 'List all files with `find`, extract function signatures, identify imports/dependencies, generate documentation').
Remove or drastically reduce the Mermaid diagram examples—Claude already knows Mermaid syntax. Instead, provide one brief example and a decision rule for when to include diagrams.
Add explicit validation checkpoints such as 'Verify all function signatures match source code' and 'Confirm dependency list is complete by cross-referencing imports'.
Move the diagram type selection table and detailed diagram examples into a separate reference file to improve progressive disclosure and reduce the main skill's token footprint.
| 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.' There are no actual commands, real code examples, or specific steps for analyzing code directories—just diagram templates showing hypothetical structures. | 1 / 3 |
Workflow Clarity | There is no clear 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. The process of going from code analysis to documentation output is completely undefined. | 1 / 3 |
Progressive Disclosure | There is one reference to `resources/implementation-playbook.md` for detailed examples, which shows some attempt at progressive disclosure. However, no bundle files are provided, so this reference is unverifiable. The main content itself is a monolithic wall of template text and diagram examples that could benefit from being 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
1930a07
- 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.