CtrlK
BlogDocsLog inGet started
Tessl Logo

c4-container

Expert C4 Container-level documentation specialist.

31

Quality

25%

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-container/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%

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 reasonable scaffolding of C4 container documentation templates with concrete Mermaid and OpenAPI examples, but it is largely placeholder-driven, lacks validation feedback loops, and references a non-existent playbook file with no actual bundle structure behind it.

Suggestions

Convert the '[Placeholder]' template fields into at least one fully worked, copy-paste-ready example so the guidance is executable rather than fill-in-the-blanks.

Either create the referenced 'resources/implementation-playbook.md' file (and a references/ directory) or remove the dangling reference, so progressive disclosure resolves to real content.

Add explicit validation/verification checkpoints (e.g. 'render the Mermaid diagram and confirm every Rel target is defined before finalizing') to lift workflow clarity above a sequence of vague steps.

DimensionReasoningScore

Conciseness

The body is mostly well-organized templates and diagrams rather than padded conceptual explanation, but it leans on lengthy placeholder scaffolding (container/API/infrastructure templates) that largely restates structure Claude could infer for C4 docs.

2 / 3

Actionability

It provides concrete templates (Mermaid C4Container block, OpenAPI yaml) the model can fill, but the core instructions are placeholders ('[Container Name]', '[Description]') rather than copy-paste-ready executable guidance.

2 / 3

Workflow Clarity

The Instructions section lists sequenced steps (clarify goals, apply best practices, validate outcomes) but lacks explicit validation checkpoints or feedback loops, and the single reference ('open resources/implementation-playbook.md') points to a non-existent file.

2 / 3

Progressive Disclosure

There are no bundle directories (references/, scripts/, assets/) and the one inline reference — 'open resources/implementation-playbook.md' — does not exist, so the disclosure structure is broken rather than well-signaled.

1 / 3

Total

7

/

12

Passed

Description

7%

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 is a vague role label rather than a capability statement: it names no concrete actions and provides no 'Use when' trigger guidance. It fails the core specificity and completeness requirements despite naming a recognizable domain.

Suggestions

Rewrite the description to list concrete actions, e.g. 'Generate C4 container diagrams and OpenAPI specs, map components to deployment units, document container interfaces and infrastructure.'

Add an explicit trigger clause such as 'Use when documenting system deployment architecture, mapping microservices to containers, or producing container-level C4 diagrams and API specs.'

Include natural trigger terms users would actually say — 'container diagram', 'deployment architecture', 'OpenAPI/Swagger spec', 'Kubernetes manifest' — to improve trigger matching and distinguish it from sibling C4 skills.

DimensionReasoningScore

Specificity

The description 'Expert C4 Container-level documentation specialist' names a domain but lists no concrete actions — it tells what role the skill plays rather than what it does (extract, generate, document).

1 / 3

Completeness

It states neither concrete capabilities (the 'what') nor any 'Use when...' trigger (the 'when'), so both halves are missing or extremely weak.

1 / 3

Trigger Term Quality

It offers no natural trigger keywords a user would say; 'documentation specialist' is role jargon, not the terms (C4 container diagram, deployment, OpenAPI) a user would naturally invoke.

1 / 3

Distinctiveness Conflict Risk

'C4 Container-level' is a recognizable niche that distinguishes it from generic documentation skills, but the lack of explicit triggers means it could still overlap with sibling C4 skills (context/component/code).

2 / 3

Total

5

/

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.