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. Use when documenting code at the lowest C4 level for individual directories and code modules.
56
Quality
53%
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 ./.agent/skills/c4-code/SKILL.mdQuality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its specialized niche in C4 code-level documentation. 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 for code documentation needs.
Suggestions
Add natural language trigger terms users might say, such as 'document my code', 'code documentation', 'API docs', or 'module documentation'
Include common file/language references that might trigger this skill, such as 'source files', 'codebase documentation', or specific language mentions
| 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 | Very specific niche targeting 'C4 Code-level' documentation specifically, distinguishing it from general documentation skills or higher-level C4 diagrams (context, container, component). The 'lowest C4 level' phrase creates clear boundaries. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%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 rather than actionable documentation. It lacks any concrete guidance on how to actually create C4 code-level documentation—no examples, no specific steps, no code snippets. The structure with sub-skill references is reasonable, but the main content provides no value beyond navigation.
Suggestions
Replace placeholder text with actual C4 code-level documentation examples showing function signatures, dependency mapping, and code structure diagrams
Add a concrete workflow with numbered steps for analyzing a code directory and producing C4 documentation, including validation checkpoints
Include at least one executable example showing how to document a real code element (e.g., a function with its signature, arguments, and dependencies)
Remove or make specific the generic 'Use this skill when' boilerplate—it currently adds no information
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The template structure is reasonably lean, but includes placeholder text and boilerplate sections that add no value. The 'Use this skill when' and 'Do not use this skill when' sections are generic and could be removed or made specific. | 2 / 3 |
Actionability | The content is entirely abstract with no concrete code, commands, or executable examples. It's a template with placeholders like '[Descriptive name]' and '[Short description]' rather than actual guidance on how to create C4 code-level documentation. | 1 / 3 |
Workflow Clarity | No clear workflow is provided for creating C4 code-level documentation. The 'Instructions' section offers only vague directives like 'Clarify goals' and 'Apply relevant best practices' without any sequenced steps or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The skill does reference 10 sub-skills with clear links, which is good structure. However, the main file provides almost no substantive content itself—it's unclear what value this overview provides versus just navigating directly to sub-skills. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.