c4-container

Expert C4 Container-level documentation specialist.

2.75x

Quality

38%

Does it follow best practices?

Impact

99%

2.75x

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

The canonical home for this skill is c4-container 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 well-sectioned set of reusable C4 container templates (Mermaid diagram, OpenAPI spec, container spec), but it leans on placeholders and generic instructions rather than a concrete, validated workflow. Its single progressive-disclosure reference points to a file that is not present in the bundle.

Suggestions

Replace the generic 'Instructions' bullets with a concrete, sequenced C4-container workflow (gather deployment inputs -> map components to containers -> draft diagram -> validate diagram/spec -> emit docs) with an explicit validation checkpoint.

Either provide the referenced 'resources/implementation-playbook.md' bundle file or remove the dangling reference, and surface any detail files as clearly signaled one-level-deep links.

Fill the OpenAPI and container templates with at least one worked, non-placeholder example so the guidance is copy-paste ready rather than a blank skeleton.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean templates and lists rather than padded prose, but the 'Output Examples' section restates points already covered in earlier sections and could be tightened, fitting the 'mostly efficient but could be tightened' anchor 3.	3 / 5
Actionability	It provides concrete scaffolds (a real Mermaid C4Container block and an OpenAPI YAML template), but these are placeholder-filled and the 'Instructions' section is generic ('Apply relevant best practices and validate outcomes'), matching anchor 3's 'some concrete guidance but incomplete'.	3 / 5
Workflow Clarity	The 'Instructions' list a rough generic four-step sequence ('Clarify goals... Apply best practices and validate outcomes...') that is not specific to C4 container work and lacks real validation checkpoints, fitting anchor 2's 'rough sequence present but many gaps; steps poorly defined; validation absent'.	2 / 5
Progressive Disclosure	Section headers organize the body reasonably, but the only external reference ('resources/implementation-playbook.md') is buried in an Instructions bullet and does not exist as a bundle file, fitting anchor 3's 'references present but not clearly signaled'.	3 / 5
	Total	11 / 20 Passed

Description

32%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 terse role label that identifies a clear niche but fails to state concrete actions or any trigger guidance for when to invoke the skill. It reads as a title rather than an actionable, trigger-rich description.

Suggestions

Rewrite as concrete actions, e.g. 'Generate C4 container-level diagrams and OpenAPI specs from deployment definitions', instead of the role label 'documentation specialist'.

Add an explicit 'Use when...' clause naming natural triggers users would say, e.g. 'Use when documenting system deployment architecture, mapping components to containers, or producing container diagrams.'

Include trigger synonyms and file/manifest hints (e.g. 'Kubernetes manifests, Dockerfiles, container diagrams') to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase 'C4 Container-level documentation specialist' names the domain but lists no concrete actions, matching the 'names the domain but actions are minimal or generic' anchor rather than the entirely-vague anchor 1 or the multi-action anchor 3.	2 / 5
Completeness	It gives a vague 'what' (a role label with no documented actions) and entirely omits 'when' to use it, matching anchor 2 ('vague what and no when') and respecting the cap for a missing Use-when clause.	2 / 5
Trigger Term Quality	Only the single keyword phrase 'C4 Container-level documentation' appears with no natural 'Use when...' trigger phrasing or synonyms a user would actually say, fitting anchor 2's 'one or two generic keywords; missing the natural phrases'.	2 / 5
Distinctiveness Conflict Risk	'C4 Container-level documentation' carves a clear niche distinct from generic documentation skills, with only minor overlap risk against sibling C4-level skills (context/component/code), matching the 'mostly distinct' anchor 4.	4 / 5
	Total	10 / 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-container/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.