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.

1.84x

Quality

50%

Does it follow best practices?

Impact

94%

1.84x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/c4-code/SKILL.md

The canonical home for this skill is c4-code in sickn33/agentic-awesome-skills

Quality

Content

43%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-sectioned and offers usable Mermaid templates, but it leans on placeholder-fill instructions rather than executable guidance, lacks validation checkpoints for batch code analysis, and references a playbook path that does not exist in the bundle. Progressive disclosure is weak: heavy template content is inlined and the single reference is mispathed.

Suggestions

Replace the generic Instructions with a concrete, sequenced workflow including an explicit validation step (e.g., parse code -> extract signatures -> map dependencies -> verify against source locations -> emit C4 Code doc).

Move the three full Mermaid examples and the template skeletons into a bundled reference file (e.g. references/diagram-templates.md) and link to it, keeping only a brief choosing-the-right-diagram table inline.

Fix the dangling reference: change 'resources/implementation-playbook.md' to a real file under references/ and create it, or remove the reference to avoid a broken pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with well-structured templates and diagrams, but large blocks of fill-in placeholder fields ('[What this function does]', '[file path:line number]') and three full Mermaid examples add length that could be trimmed without losing clarity.	3 / 5
Actionability	It provides concrete template skeletons and complete executable Mermaid diagrams, but the core instructions are mostly placeholder-fill guidance rather than executable commands, and the referenced playbook is never shown to exist, leaving key details missing.	3 / 5
Workflow Clarity	The Instructions section gives only a rough, generic sequence ('Clarify goals... Apply best practices... validate outcomes') with no validation checkpoints for what is a batch code-analysis operation; the rubric caps such skills at 3, and the absence of any concrete verify step pulls it further down.	2 / 5
Progressive Disclosure	Structure exists via section headers, but the body inlines large template and diagram content that belongs in a reference file, and the one reference ('resources/implementation-playbook.md') is not clearly signaled, uses an inconsistent path (resources/ vs references/), and the file does not appear to exist in the bundle.	2 / 5
	Total	10 / 20 Passed

Description

57%Weight 40%Scale 1-5

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 clearly communicates what the skill does with concrete, domain-specific actions, but it omits any explicit 'use when' trigger guidance and lacks natural user-facing trigger phrases, capping completeness and trigger quality. Specificity and distinctiveness are reasonably strong.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases, e.g. 'Use when documenting a code directory with C4 code-level diagrams, function signatures, or code structure.'

Include user-natural synonyms and concrete triggers like 'code-level docs', 'document this module', or 'C4 code diagram' to improve trigger term quality.

Tighten 'code structure' into more specific actions (e.g., 'class hierarchies, call graphs, module dependencies') to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (C4 code-level documentation) and lists several concrete actions ('function signatures, arguments, dependencies, and code structure'), but 'code structure' is slightly generic, leaving minor coverage gaps versus a fully comprehensive action list.	4 / 5
Completeness	Clearly states what the skill does ('Analyzes code directories to create comprehensive C4 code-level documentation'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 3.	3 / 5
Trigger Term Quality	Includes relevant terms ('C4 Code-level documentation', 'code directories', 'function signatures', 'dependencies') but lacks the natural phrases a user would say ('document this code', 'C4 diagram', 'code-level docs') and offers no synonyms or file extensions.	3 / 5
Distinctiveness Conflict Risk	The C4 code-level niche is fairly distinct from generic documentation skills, though it could still overlap with sibling C4 Component/Container/Context skills referenced in the body, leaving minor overlap risk.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/c4-code/SKILL.md
Commit: 57c135b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.