Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

c4-container

Expert C4 Container-level documentation specialist.

Quality

49%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/c4-container/SKILL.md

Quality

Content

36%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 provides a solid documentation schema (container fields, Mermaid C4Container syntax, OpenAPI template) but is padded with generic boilerplate and a duplicated paragraph, and never defines an actual workflow for producing the documentation. Placeholder templates substitute for executable guidance, and a dangling reference points to a nonexistent file.

Suggestions

Add a concrete step-by-step workflow (e.g., gather deployment configs/K8s manifests → identify containers → document fields → generate diagram/specs) with explicit validation checkpoints such as verifying each boundary against observed code.

Remove the duplicated paragraph under Dependencies and the generic Instructions/Use-when boilerplate; keep only C4-specific guidance.

Fix or remove the dangling 'c4-component-name.md' reference, and consider moving the full OpenAPI template into a reference file with a clearly signaled link from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The key C4 paragraph is duplicated verbatim (in Instructions and again under Dependencies as '#C4 containers are applications...'), and sections like 'Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.' plus the Use/Do-not-use bullets are generic filler — several padded sections.	2 / 5
Actionability	The Mermaid C4Container example and OpenAPI 3.1 skeleton are concrete and usable, but most guidance consists of placeholder templates ('[Container name]', '[Short description of container purpose and deployment]') with no executable process for discovering containers from code or manifests.	3 / 5
Workflow Clarity	Only a rough implicit sequence exists via section ordering (containers, interfaces, dependencies, diagram); the Instructions bullets ('Apply relevant best practices and validate outcomes') are abstract, steps are never stated as a sequence, and there are no validation checkpoints.	2 / 5
Progressive Disclosure	Section headers organize the ~165-line body, but everything is inlined (the full OpenAPI template is a candidate for a reference file) and the reference 'Documentation: c4-component-name.md' points to a file that does not exist in the bundle.	3 / 5
	Total	10 / 20 Passed

Description

40%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 is a short role title rather than a capability statement: it names a specific niche but states no concrete actions and gives no trigger guidance for when to use the skill. Adding an explicit 'Use when...' clause with natural trigger terms and concrete verbs would fix most weaknesses.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g. 'Use when creating C4 container diagrams, mapping components to deployment units, or documenting system deployment architecture'.

Replace 'Expert ... specialist' fluff with concrete actions such as 'Creates container-level documentation: container boundaries, interfaces as OpenAPI specs, dependencies, and Mermaid C4Container diagrams'.

Include the natural synonyms users would say — 'container diagram', 'C4 model', 'deployment architecture', 'Kubernetes manifests' — to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('C4 Container-level documentation') but lists no concrete actions; 'Expert ... specialist' is role-title fluff rather than a capability statement, matching the 'Processes PDF files' anchor of domain-named but generic action.	2 / 5
Completeness	The 'what' is vague ('documentation specialist' states no capability) and there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3; the vague what places it at 2.	2 / 5
Trigger Term Quality	'C4 Container-level' is a relevant, non-generic keyword (comparable to 'Works with PDF files'), but natural phrases users would actually say — 'container diagram', 'C4 model', 'deployment architecture' — are missing.	3 / 5
Distinctiveness Conflict Risk	'C4 Container-level' carves a clear niche with minimal conflict against generic skills, but it overlaps with closely related C4-level siblings (context, component, code) that the body itself distinguishes, so it is not fully distinct.	4 / 5
	Total	11 / 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: sickn33/agentic-awesome-skills
Path: skills/c4-container/SKILL.md
Revision: e8d346b

Reviewed: 2 days ago

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.

c4-container

Table of Contents

Is this your skill?