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.
61
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 purpose in C4 architectural documentation at the code level. It excels at specificity and distinctiveness by targeting a well-defined niche. The main weakness is trigger term coverage - users unfamiliar with C4 terminology might not find this skill when they need code documentation.
Suggestions
Add common user phrases like 'document my code', 'code documentation', 'API docs' to improve discoverability for users who may not know C4 terminology
| 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' which is a distinct architectural documentation standard. The focus on 'lowest C4 level' and specific outputs like 'function signatures, arguments, dependencies' makes it unlikely to conflict with general documentation skills. | 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 empty template rather than actionable documentation. It lacks any concrete guidance on how to actually create C4 code-level documentation, provides no examples of what good output looks like, and offers only placeholder text where specific instructions should be. The structure suggests good intentions for progressive disclosure but fails to deliver substantive content.
Suggestions
Add a concrete, executable example showing how to document a real code directory at the C4 code level, including sample output format
Replace the vague 'Instructions' section with specific steps: 1) Analyze directory structure, 2) Extract function signatures, 3) Map dependencies, etc., with validation checkpoints
Include at least one complete before/after example showing input code and the resulting C4 code-level documentation
Remove or populate the placeholder text - a skill should contain actual guidance, not a template to be filled in later
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The template structure is reasonably lean, but contains placeholder text and boilerplate sections that don't add value. The 'Use this skill when' and 'Do not use this skill when' sections are generic and could be removed or made more specific. | 2 / 3 |
Actionability | The content is entirely abstract with no concrete code examples, commands, or executable guidance. It's a template with placeholders like '[Descriptive name for this code directory]' rather than actual instructions 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 guidance like 'Clarify goals' and 'Apply relevant best practices' without any sequenced steps or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The skill does reference sub-skills and external resources appropriately with one-level-deep links. However, the main content is too sparse to serve as a useful overview, and it's unclear what value the linked sub-skills provide without any context about their contents. | 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
332e58b
- 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.