CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/c4-code/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-3

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 well-sectioned template with concrete Mermaid examples, but it leans on vague instructions and fill-in placeholders, lacks explicit validation checkpoints, and points to a non-existent reference file.

Suggestions

Replace abstract Instructions with a concrete, sequenced workflow (e.g. enumerate code elements → capture signatures/locations → map dependencies → draft diagrams → verify against source) with an explicit validation checkpoint.

Create the referenced `resources/implementation-playbook.md` (or fix the path) so the progressive-disclosure pointer resolves, and consider moving the three Mermaid examples into it.

Tighten the template by collapsing the three full Mermaid diagrams into one concise example per paradigm or linking out to a diagrams reference.

DimensionReasoningScore

Conciseness

Mostly structural and template-focused, but three full Mermaid diagrams and repeated placeholder scaffolding could be tightened; not verbose with concepts Claude knows, yet not fully lean.

2 / 3

Actionability

Mermaid templates are copy-paste ready, but the Instructions are abstract ("Apply relevant best practices and validate outcomes") and the code-element sections are fill-in placeholders rather than executable analysis guidance.

2 / 3

Workflow Clarity

A loose sequence exists (clarify → apply → provide, with an optional playbook reference) and validation is mentioned abstractly, but there are no explicit checkpoints or feedback loops for producing and verifying the documentation output.

2 / 3

Progressive Disclosure

Sections are clearly labeled, but the body references `resources/implementation-playbook.md` which does not exist, and three large inline Mermaid examples that could be split out make the overview heavier than ideal.

2 / 3

Total

8

/

12

Passed

Description

60%Weight 40%Scale 1-3

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 states what the skill does and lists concrete capabilities, but omits explicit "Use when..." trigger guidance and relies on somewhat generic specialist framing that risks overlap with sibling C4 skills.

Suggestions

Add a "Use when..." clause naming natural user triggers, e.g. "Use when creating C4 code-level docs, documenting function signatures and dependencies, or analyzing a code directory's structure."

Include common user phrasings like "document my code" or "code-level documentation" to improve trigger term coverage.

Sharpen distinctiveness by contrasting with sibling C4 layers (e.g. "for code-level detail, not component or container diagrams").

DimensionReasoningScore

Specificity

Lists multiple concrete actions—"function signatures, arguments, dependencies, and code structure"—matching the anchor for several specific actions rather than the partial coverage at level 2.

3 / 3

Completeness

The "what" is clear ("Analyzes code directories to create comprehensive C4 code-level documentation"), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Relevant terms like "C4 code-level documentation" and "code directories" appear, but common user variations ("document my code", "code docs") and explicit trigger phrasing are missing, keeping it at level 2.

2 / 3

Distinctiveness Conflict Risk

"C4 Code-level" is a recognizable niche, but the generic "Expert...specialist" framing and the existence of sibling C4 skills (component/container/context) mean it could still overlap with similar skills.

2 / 3

Total

9

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-skills
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.