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

51%

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-claude/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 body is a structured template with useful mermaid examples, but it leans on placeholder scaffolding and generic instructions rather than an executable, sequenced analysis workflow, and its single external reference is a broken path. Tightening the workflow and fixing the reference would materially improve it.

Suggestions

Replace the three generic Instruction bullets with a concrete, sequenced analysis workflow (e.g. enumerate files → extract signatures → map dependencies → render diagrams → verify output).

Fix or remove the 'resources/implementation-playbook.md' reference—either create the file under references/ and link it correctly, or drop the mention.

Add executable grounding (e.g. example grep/AST commands or a tool recommendation) so the template becomes copy-paste actionable rather than fill-in-the-blank.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with sectioned templates and a diagram-selection table, but placeholder scaffolding and somewhat redundant 'Use/Do not use' and 'Key Distinctions' sections could be tightened.	3 / 5
Actionability	Provides a concrete documentation template (signature format, mermaid diagram templates, choosing-diagram table) but it is fill-in-the-blank scaffolding with no executable commands or tooling for actually analyzing code directories.	3 / 5
Workflow Clarity	The Instructions are three generic bullets ('Clarify goals…', 'Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with no real sequenced workflow or validation checkpoints for batch code analysis.	2 / 5
Progressive Disclosure	Single file is well-sectioned, but the one external reference—'resources/implementation-playbook.md'—points to a non-existent path (no references/scripts/assets bundle exists), so navigation is not reliably signaled.	3 / 5
	Total	11 / 20 Passed

Description

58%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 names a clear niche and several concrete actions but omits any explicit 'Use when...' trigger guidance, leaving the activation context implicit. Adding natural trigger phrases would lift both completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when documenting a code directory's functions, classes, and dependencies at C4 code level.'

Add user-natural synonyms such as 'document code', 'code structure analysis', or 'map function dependencies' to broaden trigger coverage.

Clarify the boundary versus sibling C4 skills with a one-line distinction in the description itself.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions—'function signatures, arguments, dependencies, and code structure'—against the C4 code-level domain, with only minor coverage gaps.	4 / 5
Completeness	Clearly states what the skill does but provides no 'Use when...' trigger clause, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant terms like 'C4 code-level documentation', 'code directories', and 'function signatures', but misses common natural variations users would say such as 'document code' or 'code structure analysis'.	3 / 5
Distinctiveness Conflict Risk	The 'C4 Code-level' niche is mostly distinct from sibling C4 skills, with only minor overlap risk against component/container/context variants.	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-claude/skills/c4-code/SKILL.md
Commit: 57c135b

Reviewed: 21 hours 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.